further update. I tested this as a package in a stand alone TS using cmd line wusa Windows6.1-KB2862330-v2-x86.msu /quiet /norestart /log:C:\Temp\logfile.log it rebooted despite the above /norestart, configuring updates appear after reboot then it rebooted again itself. A log file was created but its not completely readable in trace or notepad (ignore that there is no /log switch)
I've then manually uninstalled it, prompted for a reboot (as expected), configuring updates appear after reboot, then back to ctr+alt+del and it restarts itself again!! tried as via normal SWD no TS, installs fine and no reboots, execmgr shows reboot required but so far no reboot. be good to know what others have found. hope it helps.. On 23 January 2014 15:05, Rickym61 <[email protected]> wrote: > yes getting issues with 1st update, was getting the errors in smsts.log > mentioned in the KB during the new image I was creating, I've removed it > and it worked, just going to test creating it as a package and then in its > own TS to see if can still be deployed via a TS or just not via the Install > Software Updates step in a TS.. > > > On 23 January 2014 14:20, David O'Brien <[email protected]> wrote: > >> Hi all, >> >> just a quick poll: >> Has anyone seen any issues with latest January 14 Win7 Updates KB2862330 >> & KB2913602 causing OSD issues due to double reboot? >> Got a customer where one of those updates seem to cause problems and I >> quickly wanted to check if others are seeing this or if I really need to >> dig a bit deeper there. >> >> http://support.microsoft.com/kb/2894518/en-us?sd=rss Is not listing any >> of those two. >> >> Thanks, >> David >> >> > >
