Repository navigation
Update-WinGetPackage, RebootRequired and error 3010 #5676
Rob Nicholson (munrobasher)
started this conversation in
PowerShell
Replies: 1 comment
|
Yes — in practice, treat 3010 itself as the reboot signal. 3010 is the standard installer code for "success, but a restart is required to finish the installation," so an update reporting 3010 is not a failed update. Since RebootRequired stays False in your runs, I would handle it in your script like this:
In short, for your script: trust the 3010 code over the RebootRequired flag, and let the reboot happen before you judge whether the update worked. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Recent convert to WinGet, I've put together a simple PowerShell script to update packages. Pretty simple. It reports if there is an InstallerErrorCode returned and also whether RebootRequired is true.
However, I've noticed that a) RebootRequired has never been true but b) some updates report error 3010 as shown below. A search reveals that some packages return this error code indicating that a reboot is required. Simple enough for me to modify my script to handle this case but why isn't RebootRequired getting set instead and is error code 3010 always reboot required?
All reactions