You might learn something from the actual error logs- setuperr.log, setupact.log.
But they are far from obvious. Without the expertise of a couple of people who spent some days on some cases in the past, it's a matter of research and being lucky.
And there may be something in my previous post that helps.
Thanks, just looked for those and I don't have them, but apparently they are only created when an install is successful?
Also, regarding this post:
https://answers.microsoft.com/en-us/...6-9cd1b3eac449
The poster found a reference to smconfiginstaller but what file would he have looked at to determine the error? It's not made clear in the post even though he does reproduce the contents of the file.
In a previous thread, you mentioned trying to install KB5003635 (CU Jun 2021) and it failed.
To summarize your updates:
SSU July 2021 solved the Servicing Stack pre-req for CU Jun 2021, so that's not a blocking factor.KB4601556 .NET 4.8 May 2021
KB4516115 Adobe Flash Security Sep 2019
KB4517245 Enablement Package
KB4524569 SSU Nov 2019
KB4528759 SSU Jan 2020
KB4535680 Secure Boot DBX
KB4537759 Adobe Flash Security Feb 2020
KB4538674 SSU Feb 2020
KB4561600 Adobe Flash Security Jun 2020
KB4577586 Adobe Flash Removal
KB4589211 Intel Microcode
KB5003244 SSU May 2021
KB5004748 SSU Jul 2021
KB5003169 Monthly CU May 2021
I'm inclined to believe it's possibly from incompatible drivers. Try to see if there's updated W10 drivers for your system, install them and then retry the upgrade process. Setup performs a lot of compatibility checks for in-place upgrades -- but does a TERRIBLE job reporting the failed checks.
You should have some. The point is they record events- plenty of examples of them on tenforums for failed upgrades.Thanks, just looked for those and I don't have them, but apparently they are only created when an install is successful?
You have to look in the right place for the phase in which the failure occurred. I think I posted the appropriate links above.
Or- you could use a 3rd party fast search tool (as you're searching for system files) such as Everything (popular) Locate32 (which I like) etc.
2021-05-11 13:57:10, Error CSI 00002181 (F) Generic Command ErrorCode: 80004005 Executable: SMConfigInstaller.exe ExitCode: 3222072836 Phase: 38 Mode: Install (first install) Component: WCF-GenericCommands, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versionScope=NonSxS[gle=0x80004005]
etc comes from setuperr.log
----------------------------------
Notice what setupdiag.exe does.
https://social.technet.microsoft.com...diag-tool.aspx
It creates a zip file with the relevant log files where you run it from.
So you should be able to find the extracted log files there.
Noted, thanks. Now found setupact.log and setuperr.log in the c:\windows folder
Curiously enough the setuperr.log file is empty, zero bytes. Is that normal?
To read setupact.log I had to copy it elsewhere then open it, however looking through it I see no indication of any problems. If it helps the last lines in the file are:
AudMig: Running offline, detecting if HDAudio persistence is needed.AudMig: HDAudio persistence not required, remaining offline.2023-03-31 18:01:19, Info MIG MigHost started with command line: {CF49BDA6-8014-42B1-A542-8488E7244DBD} /InitDoneEvent:MigHost.{CF49BDA6-8014-42B1-A542-8488E7244DBD}.Event /ParentPID:15456
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::Init: Successfully initialized surrogate.
2023-03-31 18:01:19, Info MIG MigHost: Initialized successfully with CLSID[{CF49BDA6-8014-42B1-A542-8488E7244DBD}] and LogDir=[]
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer in progress: BinaryPath=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0].
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: ThreadID=[0x198c], Server=[C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll], CLSID=[{D26AA4A5-92AD-48DB-8D59-95EF0DCE6939}], ApartmentThreadingModel=[0]
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Loaded server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::LoadAndRegisterServerInThreadContext: Successfully loaded and registered server(C:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-RasServer-MigPlugin\RasMigPlugin.dll)
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: LoadAndRegisterServerInThreadContext() succeeded.
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::LoadDllServer finished: Result=[0x0].
2023-03-31 18:01:19, Info MIG MigHost: CMigPluginSurrogate::COMGenericThreadingHostThreadProc: Exiting ThreadID=[0x198c].
2023-03-31 18:01:19, Info MIG MigHost: Exiting process.
EDIT: Actually, maybe ignore the above - found the logs.zip file as created by SetupDiag and that has a huge setupact log file. Just looking at the last lines there are a few errors:
2023-03-31 18:09:34, Error [0x030153] CMI Callback_CMI_ConfigInstall: CBS startup processing failed.
2023-03-31 18:09:34, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.]
2023-03-31 18:09:59, Info [0x070042] DIAG CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
2023-03-31 18:09:59, Info DIAG CallBack_DiagnosticDataSend: Setup was started from Phase 4. Disabling Diagnostics [DiagnosticDataSend] in this scenario
2023-03-31 18:09:59, Info [0x090095] PANTHR WdsExitImmediate called! Execution will stop, and the queue won't be saved.
2023-03-31 18:09:59, Info [0x030023] CMI Callback_CMI_ConfigInstall: Exit.
2023-03-31 18:09:59, Info [0x09008c] PANTHR SeqExecute -- stopping, since WdsExitImmediate() was called
2023-03-31 18:09:59, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2023-03-31 18:09:59, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2023-03-31 18:09:59, Info [0x090086] PANTHR pWorkerThreadFunc -- Stopping
2023-03-31 18:09:59, Info PANTHR DeleteCriticalSection for pExecQueue->csLock;
2023-03-31 18:09:59, Info [0x0605a6] IBS Requested UI to hide the language and locale selection pages.
2023-03-31 18:09:59, Info [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)
2023-03-31 18:09:59, Info [0x0601d7] IBS InstallWindows:Error Type = 3211266
2023-03-31 18:09:59, Info IBS InstallWindows:Exiting with return code [0x1F]
2023-03-31 18:09:59, Info [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.
2023-03-31 18:09:59, Info SP WINDEPLOY error code is 0x8007001F. Will not attempt uninstall
2023-03-31 18:09:59, Info CBS Trusted Installer signaled for shutdown, going to exit.
2023-03-31 18:09:59, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_NOTIFICATION:PRESHUTDOWN
2023-03-31 18:09:59, Info CBS Ending the TrustedInstaller main loop.
2023-03-31 18:09:59, Info CBS Starting TrustedInstaller finalization.
2023-03-31 18:09:59, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2023-03-31 18:09:59, Info CBS Ending TrustedInstaller finalization.
- - - Updated - - -
Thanks. If I want to check if all of the W10 drivers are up to date is there a way to automate that or do I need to check them all manually via Device Manager and right click, Update Driver on each one? If the latter it could take a while.
As to drivers- it's likely there will be more than are associated with devices listed by Device Manager.
If you now have a setuperr.log, see that first.
Given the last update you listed it seems you are fully up to date with 1909:
https://support.microsoft.com/en-us/...5-b6e1ff506d64
What led to your staying with that build? Did you choose to do that, or simply not realise you were not receiving updates?
While a have a setuperr.log file in the Windows folder that log file is unfortunately empty. Is that normal?
I left the older PC on that build because it wouldn't let me upgrade past 1909 some years ago despite many attempts. I grew tired of being nagged about it by Windows so installed Shutup10 and basically forgot about it ....... (and it had the nice side effect of improving the PC's privacy and removing various annoyances). I've since set the defaults back to 'factory' via Shutup10.
As far as I recall there should be 2; have you checked in the zip file created by setupdiag.exe?
Note from the link I posted previously, these log files are placed depending on the upgrade phase that failed, so you could be looking in the wrong place.
0xC1900101 - 0x30018 Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
Contact your hardware vendor to obtain updated device drivers.
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. A device driver has stopped responding to setup.exe during the upgrade process.
https://learn.microsoft.com/en-us/tr...umb%2Ftoc.json
I suggest you scan the log files looking for references to any driver file.
E.g. you could search for .sys for starters.
Have you had any 3rd party security software installed?
--------------------------------------
You could try using the
Windows Update Assistant
(Google/search for that).
There's a chance you might learn something more.
Last edited by dalchina; 01 Apr 2023 at 14:22.
I'll do a search for any other instances of setuperr.log
As for security software, all that the PC has installed is Eset NOD32 and Malwarebytes.
I'll search through the logs.zip file that SetupDiag created to see if there are any mentions of drivers and any relevant mentions of issues with one or more.
Thanks.
One of the standard recommendations is to uninstall security programs fully if you have problems, but that may have nothing whatsoever to do with the actual issue of course.
Quote