kirb
Audit mode gets stuck at “Configuring updates” on reboot
When installed in audit mode, after installed prerequisite update, Legacy Update stucks on "Configuring Update" like this:
In the test it stucked for nearly an hour without any progress. If forcibly restarts, the update will successfully installed but not Legacy Update itself. Hoping for the problem to be fixed.
Latest Legacy Update (version 1.11) is used
I had this same problem the other day. I left it on "Configuring Update" over night and nothing. The way I solved the problem is a bit of a work around. Legacy update downloads the files it needs to update windows to c:/programdata/legacyupdate. Legacy update does delete that folder after the update process is over but if it fails, the folder with the update files might still be there. I installed the service packs from that folder and legacy update worked without a problem after that.
WU engine is blocked by design in audit mode installing .msu files = WU engine
in normal mode, if WU settings is not set to manual search for updates, installing .msu files can get stuck this affect Win 7 -> 8.1 without updated WU Client that fixes the long stuck search bug
Vista is also affected, but it doesn't have any wuaueng.dll that fix the issue
WU engine is blocked by design in audit mode installing .msu files = WU engine
in normal mode, if WU settings is not set to manual search for updates, installing .msu files can get stuck this affect Win 7 -> 8.1 without updated WU Client that fixes the long stuck search bug
Vista is also affected, but it doesn't have any wuaueng.dll that fix the issue
so could it be solved ？
so could it be solved ？
Solve what? you can extract the inner cab file and install with DISM tool
WU engine is blocked by design in audit mode
This is a pretty terrible design, then... you use audit mode (Ctrl+Shift+F3 during OOBE) to prepare a system outside of OOBE with drivers and updates, then you let it go back to OOBE when done. Clean way to set up a computer for someone. Why in the hell would WU engine be unavailable in audit mode?
Got a Windows 7 laptop stuck at "Please Wait" after Legacy Update installed SP1 on a clean startup of a recovery partition... no easy or obvious way out of it other than to nuke it and restore it a 2nd time.
Would be nice to, you know... not have that happen.
@FalconFour As of 1.12, you can reboot to safe mode to break out of setup mode. I haven’t tested if this correctly handles resetting back to audit mode though.
@kirb I had just installed it today on a freshly restored Dell Latitude E5510 (restored using the Dell image, from "Repair my computer" boot menu). So that was definitely 1.12. Unfortunately, Safe Mode was among the things I tried. It just stays locked at "Please Wait" while the system remains idle, yet responsive to Power button (goes to sleep/hibernate). It was unattended, though (downloading took a long time, so I walked away and came back in an hour or so). I first saw it at "Preparing for first use" (black screen with animated line), but crashed it off after ~20min of waiting there with no disk/CPU activity.
Second time around, after restoring again and going through OOBE with a real account (hate doing that, feels "ugly"), it seems to be going well... Legacy Update popped up over the "please wait" curtain and started installing more updates on the pre-login screen.
edit: Yep it all works perfectly with a normal account lol
Thanks for the info. I’ll need to do more testing of audit mode soon, I didn’t get a chance to do that for 1.12. Most likely what I’ll do is, if the system is already in audit mode, we’ll use runonce instead of setup mode. The audit mode Administrator account logs in automatically with no password, so it’ll still be automated.
It shouldn’t have issues installing updates in audit mode any more, because we directly use dism/pkgmgr rather than Windows Update. It’s just a matter of keeping in audit mode so we don’t break the state of the system.