Re:Introducing PackageManagement in Windows 10
by level on Wednesday April 29, 2015 @01:42PM
(#9460121)
I don't even mind the multiple restarts, the part that bothers me is that I have to babysit Windows Update as soon as my machine finishes restarting, tell it to get updates, tell it to install now, and then have it restart again. If Windows Update could collect all the update packages, and I could leave it alone for 20 minutes and come back to a fully updated system, that would be fantastic.
[ Parent
| on HN ]
Re:Introducing PackageManagement in Windows 10
by glesica on Wednesday April 29, 2015 @02:01PM
(#9460320)
Yeah, this seems like it should be pretty straightforward (I'm sure it is harder than it seems, but still). Set a flag that persists through multiple reboots that says "after Windows loads, if there are updates, apply them and reboot, repeat, otherwise unset the flag".
Re:Introducing PackageManagement in Windows 10
by tomswartz07 on Wednesday April 29, 2015 @02:28PM
(#9460577)
Fun fact: I helped tweak up a Powershell script that does this exact thing:
https://github.com/tomswartz07/packer-windows/blob/master/sc...
Re:Introducing PackageManagement in Windows 10
by tacticus on Wednesday April 29, 2015 @09:34PM
(#9462846)
I owe you a reasonable beverage of your choosing. Please redeem anytime you're in melbourne.au :)
Re:Introducing PackageManagement in Windows 10
by seanp2k2 on Wednesday April 29, 2015 @02:08PM
(#9460388)
If only it had a place to register a setting or store a file containing information like "update until you reach the latest version". It'd also need to be able to get through all the updates without crashing even once (otherwise we'd need to check the disks and repair start-up files, and that can't be automated), so maybe this is just impossible.