Windows 8.1 errors before Windows 10 upgrade

Did not receive notification of answer... sorry for delay Peter...

Fixlog.txt information you wish is i suppose :

Code: 
========= sc query wuauserv =========




SERVICE_NAME: wuauserv
        TYPE               : 20  WIN32_SHARE_PROCESS 
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_PRESHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0


========= Fin de CMD: =========




========= sc qc wuauserv =========


[SC] QueryServiceConfig r‚ussite(s)


SERVICE_NAME: wuauserv
        TYPE               : 20  WIN32_SHARE_PROCESS
        START_TYPE         : 2   AUTO_START  (DELAYED)
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : C:\Windows\system32\svchost.exe -k netsvcs
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Windows Update
        DEPENDENCIES       : rpcss
        SERVICE_START_NAME : LocalSystem


========= Fin de CMD: =========

File is attached :
 

Attachments

FRST Registry Search
  1. Click the Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Server Manager or Windows Features dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.

  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste amd64_microsoft-windows-r..component.resources_31bf3856ad364e35_6.3.9600.19990 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

here goes

There is an error though :
registry key not found for HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-r..component.resources_31bf3856ad364e35_6.3.9600.19990_fr-fr_8178f44066adaf79
 

Attachments

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Capture Process Monitor Trace
  1. Download and run Process Monitor. Leave this running while you perform the next steps.
  2. Try to install KB5007247 again.
  3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
    i3yiUac.png

  4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
  5. Zip up and attach the file LogFile.PML.
  6. Copy the cbs.log to your desktop, zip it and attach the zipped cbs.log as well.
 
Unfortunately i don't think PSMon will give you any results... (I did capture though installation stage, but first attempt was a file of 4GB, and a zip of 200MB)...
Will redo with filtering

In the KB5007247 case, it does install correctly in WU. It then goes in a reboot stage (step 1/3, 2/3) where it fails before Windows is loaded, and reverts installation.
It then finishes rebooting in preceding stage .. And ask's to install it once more...

Here goes for CBS... will restart install with PSMon filtering to narrow and remove useless lines (TeamV and MS Security Essential)

And for rememberance of installations :
1639384280719.png

What is weird is this :
1639384637331.png

It seems another KB is installed (KB3185331) instead of awaited KB (KB5007247)

After reboot and WU searching updates :
1639384906568.png
 

Attachments

Last edited:
dmp filtered is 164 Mb (zipped) ... is there any better filter to use ? wupdate / Tiworker (or other ?)
I don't even think i can dumped file here directly
 
Got an ultra-filtered logfile.... Removed all success events to keep only the rest of events... Hope it helps out (File is RAR archive)
 

Attachments

The attached files do not line up meaning the ProcMon log is useless.
Attach the file C:\Windows\INF\setupapi.dev.log to your next reply.
 
I'm really sorry for the mess peter...
I still believe that problem being at reboot stage (at 2/3 stage after machine reboot)... PSMon would in anycase be useless unfortunately.


Here goes for the setupapi.dev.log file awaited in zipped file
 

Attachments

wondering if we are not taking the problem on the wrong side... Main goal is to upgrade to windows 10....
My habits is a normal upgrade works well when all system is uptodate.
Except Monthly update for october, system is uptodate.
Yes i know you will state that nevertheless CBS / DSIM is not clean...

But should we not try rather to analyse why w10 upgrade fails ? maybe it would round up issues that messes up also win 8.1 ?
My 2 cents of a non expert though..
 
Edit: upgrading a corrupted Windows OS is never good as the corruption may not be fixed. Only a clean install will remove the corruption.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Not sure if fixlog is the good one... FRST shut down without error message, had to restart a second time (each in administrator mode) and got the log enclosed at 2nd run.
 

Attachments

It looks like there are some folders and files missing.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Hello Peter..

Sorry for late reply, was on business travel, and had no access to computer meanwhile..
Here Goes for return
 

Attachments

ran a sfc scannow after reboot.
results in cbs.log joined..

now lauching a WU
 

Attachments

cbs.log post update

Installed with success but WU still wanting to install it...
1640115921625.png1640115876752.png
 

Attachments

You must log in or register to reply here.
Back
Top