Just installed Plex-1.0.0.792-d4adb056-x86_64.exe on my Windows 10 desktop. It started to reboot without any prompt but luckily I was able to ctrl+alt+del to interupt it and save what I needed. Please don’t auto reboot, if that is indeed what the installer does.
Also, I don’t think there’s a suitable ‘tag’ when creating posts for the new plex app, hence tagged as plex-media-player.
I can imagine that this may happen if you had other Windows updates waiting to get installed anyway.
“Patch day” has been upon us recently. So the Windows update mechanism may have reared its head.
Yep. And it’s a major patch cycle this month, Microsoft fixed a couple serious vulnerabilities. All of my Windows 10 machines quickly got the update. That could be a factor in this.
Can confirm that some patches were installed last night on the main PC. It looks like the final step (vc runtime install) hit some issues with locked files, perhaps. Event log examples:
Product: Microsoft Visual C++ 2017 X64 Minimum Runtime - 14.16.27024. The file C:\WINDOWS\system32\msvcp140.dll is being used by the following process: Name: OfficeClickToRun , Id 4696.
Product: Microsoft Visual C++ 2017 X64 Minimum Runtime - 14.16.27024. The file C:\WINDOWS\system32\msvcp140.dll is being used by the following process: Name: firefox , Id 15528.
Happened to me just now too. All of the latest W10 updates were installed yesterday and no updates have been installed since then. All of my stuff closed and asked if I wanted to force restart, I canceled it and all that was left was Outlook and the finished Plex installer.
Yes, happened to me too just now, Thursday, August 15. Windows reports that this morning’s update check showed no updates needed.
Funny thing was windows told me the only app that’s keeping me from rebooting (I was shocked for a moment since I didn’t order a reboot) was … the Plex install app still running. Oh well. I think no harm done.
Happened to me, too. Here’s what I see in the Event Log:
The process C:\Program Files\Plex\Plex\vc_redist.x64.exe (DESKTOP-B6MT3FM) has initiated the restart of computer DESKTOP-B6MT3FM on behalf of user DESKTOP-B6MT3FM\[me] for the following reason: Application: Installation (Planned)
Reason Code: 0x80040002
Shutdown Type: restart
Comment:
I installed it on four different Windows 10 1903 systems, all are completely caught up with Windows updates (because of the reported worm), and all four performed a reboot after installing, with no prompts, no warning. Two of the systems are desktop computers, one is a laptop, and another a Surface Pro 3.
Clearly the latest release is forcing a restart at the end.