Googling for the error text led me to this post on the Microsoft forums, describing a similar problem. So it seems that it was trying to load a user account with SID ending in -500, and failed.
20:17:42, Error CSI (F) base\wcp\rtllib\inc\auto_hive.h(105): Error STATUS_OBJECT_PATH_NOT_FOUND originated in function Windows::Rtl::AutoHive::Load expression: (null) What I did was, after my computer failed to install, and rolled back the installation again, was open this log file in Notepad++, then searching for entries with Error. This log file will also be created as part of the standard system file checking done by installing Windows Updates.
The result of running this check is a (sometimes huge) log file called CBS.log, located in %WinDir%\Logs\CBS\CBS.log One of those tips is running sfc /scannow. Most of the forums describing the problem were either abandoned, or given the basic generic troubleshooting tips, which are rarely useful (all they tell you there’s a problem, as if you didn’t know). TL DRĪfter failing to install the update, from both Windows Update and manually downloading it, I turned to the web, trying to find solutions. In my particualr case, (temporary) enabling the Administrator user (after running sfc /scannow in an elevated prompt, followed by net user administrator /active:yes) allowed the update to install successfully! After installing and rebooting the machine, I disabled the built-in Administrator account using net user administrator /active:no from an elevated prompt. This can serve as a general troubleshooting step when google searches lead you nowhere.
I’m writing this post mainly to myself, explaining how I figured out why this particular Windows Update package was failing to install on my Windows 10 (installation began, then rolled back).
0 kommentar(er)
