Hey everyone! I'm in the process of deploying Windows 11 upgrades to our eligible machines using PDQ Deploy. I'm currently executing the Windows 11 installation assistant with a command that looks something like this: `Start-Process -FilePath "C:TempW11UpdateWindows11Update.exe" -ArgumentList "/QuietInstall /SkipEULA /NoRestartUI" -NoNewWindow`. I'm searching for a way to prevent the PC from rebooting immediately after the installation. I've tried tweaking some flags, including the `/NoRestartUI` option, but no luck so far. Has anyone figured out a working solution that I can use as a reference? If I have any success myself, I'll definitely share the results!
5 Answers
Here's a suggestion: maybe run the upgrade only when no one is logged in. You can display a message during the upgrade and allow it to reboot when done. I work in a hospital, so I know how important uptime is for users, but sometimes you just have to do the upgrade and reboot for security reasons. Good luck!
Have you considered allowing Windows Update to handle it? That way, you can use the Active Hours and 'select a reboot time' features available through Windows.
We’re actually not looking to upgrade to Windows 11 yet since they said we have until October, so there’s no rush.
I used to have the `/NoRestartUI` flag in my upgrades with the Windows 11 Upgrade Assistant via PDQ, but it caused automatic restarts, so I removed it. Now, it just prompts the user to restart instead. You might have better luck with this approach!
Sounds good! Will it give them a 30-minute timer to respond, or will it reboot immediately? That's really what I want to avoid.
You could try adding the `/NoReboot` flag alongside other parameters. Something like: `setup.exe /EULA Accept /auto upgrade /migratedrivers all /dynamicupdate disable /telemetry disable /compat IgnoreWarning /showoobe none /NoReboot` might do the trick!
Thanks for the tip! I’ll give that a shot and let you know how it works out tomorrow.
This does sound like a better approach, but catching all PCs that are idle is tough, and warning users of an impending reboot can be difficult. I might have to go this route regardless.