Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, October 31, 2018 1:42 AM
I am the IT guy for a company in Charlotte that has 14 on-site desktops and 4 Windows 10 virtual machines. For over a decade, the virtual machines ran the company's POS software with Windows XP and Office 2003 without incident. However, the company moved to a new location in July, and I took this occasion to upgrade their hardware and migrate the company to Office 365. Since Office 365 doesn't work on XP, I bought 4 Windows 10 Pro licenses from Newegg and set up new virtual machines with W10 + O365 for the remote users. This is all being hosted via VirtualBox, by the way, because [reasons].
Three users have no problems whatsoever. However, one of the virtual machines shuts down randomly due to event ID 1074:
“The process C:\Windows\System32\RuntimeBroker.exe (COMPUTERNAME) has initiated the power off of a computer (COMPUTERNAME) on behalf of user DOMAIN\REMOTEVMUSER for the following reason: Other (Unplanned)”
The virtual machines are all logged in to the same domain under the same user. Since moving to hosted Exchange in 2011, I've used the same username, since the only thing that differs on each VM is the Outlook profile and the login for their POS app; it's a lot less work than creating a new user profile every time.
In this thread I discussed everything I'd done to that point: moved the VM to a different server, cloned a working VM and entered the user's O365 and POS accounts, did in-place reinstalls of Windows 10 on the host and guest, created a new AD user, upgraded to the October Update, deleted the VM and created a new one from scratch, etc. And NOTHING has stopped these daily 1074 shutdowns.
On Monday I took one of the company's old desktops - which I reformatted back in July - and set it up for this user. And it shutdown this afternoon, with the same error message. Frankly, I don't even know how it's possible for RUNTIMEBROKER.EXE to be shutting down a computer under all these circumstances: old virtual machines, new virtual machines, new physical machines. Seems like the only thing all these have in common is the Office 365 account.
I have a support ticket in with the Office 365 team, but I have no confidence that they'll be able to solve the problem. Googling this problem comes up with almost nothing. Is there ANYONE out there that can help?
Thanks!
All replies (12)
Thursday, November 1, 2018 9:03 AM
Hi,
This kind of restart caused by RuntimeBroker.exe is triggered by auto Windows Update.
Please configure the auto-restart with the following link:
Manage device restarts after updates
By the way, I noticed you capture this Windows 10 ISO image with clone, however clone will not remove computer security ID, and will bring risk to system.
Bests,
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, November 1, 2018 11:58 PM
Hello!
1) Why would Windows Update shut the computer down? I've heard about WU restarting at awkward times - I've never heard of of Windows Update initiating a shutdown.
2) What am I supposed to do with your link? It's all about scheduling reboots and setting "active hours". WU isn't rebooting the computer - it's shutting it down. Also, I disabled the Windows Update service on the user's physical machine and it still shut down.
This is the only computer on the domain having this problem, so I don't think Group Policy is the problem here.
Saturday, January 19, 2019 9:49 AM
Were you able to ever get anywhere with this? I have my personal computer I built ~6 months ago or so and ever since I built this new machine I have been having these same issues. If I ever fall asleep early with my computer on, when I wake up it tends to be powered off 90% of the time even though I did not do it, sometimes I have things running or leave things open and plan on coming back to them if I fall asleep. Every morning when I turn it back on and check out event viewer, it always seems to be around 9:45-10:45 that the computer initiates this auto shut down. I know it is not Windows updates and that type of cop out excuse and BS link to an article completely unrelated to the problem that someone above posted is ridiculous. The computer is fully powering down when it should not be for no reason and is being initiated by the computer itself. I have sleep mode and other power options disabled and cannot figure out why this machine keeps doing it to itself but none of my other machines in the past have.
For what it's worth, in one of my logs after the 1074 shutdown, there was another log stating the computer was being shut down as "part of the customer experience improvement program". I have tried to disable this however MS has removed any entries of this from the control panel that used to be there in previous version of Windows, even previous versions of 10. I was able to go into group policy editor to fully disable this, as well as any related tasks from the task scheduler. I am hoping going forward this may solve my issue but it is beyond aggravating dealing with this for so long and it is even more upsetting to get some BS response from a MS rep saying it's because of updates shutting down the computer without even reading or acknowledging the actual post.
Thursday, February 7, 2019 3:36 PM
Hello,
Did anyone solve this problem? I am experiencing this same problem in Azure running 4 Windows 10 VMs in North Europe. And all the VMs have got the same problem at different times during the past 4 days. From 1-3 shut downs every day.
From the Azure portal I receive this error:
This virtual machine is stopping as requested by an authorized user or by a process running inside the virtual machine
Does anyone have an answer how to fix this?
Best regards,
Sondre
Saturday, March 9, 2019 10:38 PM
I am having the exact same issue with a 3 month old Windows 10 Pro machine that randomly decides to shut down on its own Event1074,User32 with the same info as laid out above. Doe anyone have any ideas on this ??
Rich
Monday, April 15, 2019 6:54 PM
One of my users have the same issue on Windows 10. I ran Windows update check and installed a bunch of updates. Will post an update next month.
Sunday, April 28, 2019 3:40 PM
I'm seeing the same problem on one of my Windows 10 Pro machines - and I can't see that shut downs and restarts are associated with Windows Update since these tend to be flagged as being driven by svchost not RuntimeBroker. Rather frustrating as I have some items running from start up that can't be set as services so need a manual intervention after each reset.
Monday, July 29, 2019 9:58 AM
I'm seeing similar results occurring - I have a Win10 Pro PC (HP Prodesk 600 i7-8700 16Gb 512Gb SSD) PC. It's been set up to act as a Term Server (With RDP Access). We have various staff members logging in remotely throughout the day and it will randomly restart without warning.
It does have an Office 2019 Standard OPEN Lic activated on it. (And at the time of install - enabled auto updates to Office)
This is a recent addition to their LAN - (Migrated from a similar box running Win7 Pro + Office 2007 Open Lic) with the same features. No reboots happening on the legacy box.
The new box does have Win10 Pro (1903) + Office 2019 OPEN Std Lic.
After checking the event logs, strange message appeared for a user logged on remotely via RDP... "....RuntimeBroker.exe has initiated a shutdown..." - So I suspect when I installed Office 2019 there was an option to enable auto updates for Office 2019. I enabled this option and all User Acct Logins were enabled for Office 2019 Auto Updates.
Given there is no real way of controlling Windows 10 Updates - (Inclusive of Office 365 / 2019 updates) I've come to the conclusion that Office 2019 updates have occurred throughout a user account login remotely, and it initiated a reboot. After this reboot, Office 2019 required re-activation on the Open Lic on this pc... which also leads me to suspect an auto Office 2019 update. (And broke it).
So I have now re-activated the Open Lic - and now disabled all Auto Updates in Office 2019.
I have confirmed the Auto Update option is now disabled for all user accounts to this new Win10 Box.
But I am not yet certain whether it will occur again.
So any feedback WRT to the above or confirmation would be good. I'll know more over the next week if a reboot on this box re-occurs again. My hunch is it's Office 2019 updates causing the problem. Turn off Auto Updates.
Rgds Gerry
**
Updated 7th Aug 19 16:17 AUST WST
Further update - The Office 2019 Updates now disabled and reboot did not fix the problem. The pc still auto intermintently reboots with a remote RDP session. As described above.
Wednesday, August 7, 2019 8:18 AM
I had seen this issue on Windows 2016 STD edition. RuntimeBroker.exe has initiated the Poweroff the computer. There is no proper information in the event log. Anyone raised a ticket with MS and get the solution?
Wednesday, August 21, 2019 5:41 PM
Just voicing that I am also experiencing this issue - RuntimeBroker.exe initiating a SHUTDOWN on behalf of user. Windows 2016 Standard RDS server.
EDIT: Disregard my comment. The user admitted to accidentally shutting down the computer. :)
Sunday, November 10, 2019 1:19 AM | 1 vote
I run into this issue frequently troubleshooting in the field. I often find it's a power issue. I'll typically run SFC/DISM, then try a clean install. That effectively eliminates all software causes. The issue seems to be load sensitive, you'll find it triggers more consistently with a heavier wattage draw.
If the issue persists after eliminating software and is determined to be load sensitive, I throw in a new PSU, and it always fixes it.
Friday, July 17, 2020 9:10 AM
Does that apply to laptop as well? I have an asus a75 i7 16gb 2 ssd’s 1tb/500gb and that started a couple months ago. I’ve thought it was related to a dual boot with centros and uefi but it isn’t. Thank you in advance.