[SOLVED] Win10 - refuses to update to 22H2

Another interesting data point. When I was reanabling devices in bios, I noticed that the minitool backup boot menu was still active. So I popped in and found a very old version of their software. It refused to update itself for some invisible reason. I turned off the boot menu co pletely now.

But also found in partition manager that there appears to be 2 or maybe 3 recovery partitions in various stages. Might be best to remove all that and start fresh?
 
well, at this point, nothing worked. Still died at the same point, apparently after updates applied. I tried ti with everything turned off in bios and with it all back on, no difference. It's gettung MUCH further than ever before, but still no success to finish.

this seems odd
1677461877611.png
 

Attachments

dsalch said:
But also found in partition manager that there appears to be 2 or maybe 3 recovery partitions in various stages. Might be best to remove all that and start fresh?
Click to expand...
Hi,

The partitions looks good, and the unallocated space we can ignore. Please run the ComponentsScanner again and report the result.
 
It appears that it is not possible to leave the insider program after this amount of time, because it requires a "revert back" to a previous version, which isn't on this machine any more .
 
Could you please post a screenshot of Updates & Security > Windows Insider Program, I wonder if it still show the message "your device is set up to get insider preview builds".

Please run the following commands as well and copy and paste the result.
Code: 
sc query wisvc
sc qc wisvc
 
Microsoft Windows [Version 10.0.19042.1165]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sc query wisvc

SERVICE_NAME: wisvc
TYPE : 30 WIN32
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

C:\WINDOWS\system32>sc qc wisvc
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: wisvc
TYPE : 20 WIN32_SHARE_PROCESS
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:\WINDOWS\system32\svchost.exe -k netsvcs -p
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Windows Insider Service
DEPENDENCIES : rpcss
SERVICE_START_NAME : LocalSystem

C:\WINDOWS\system32>
 
The warnings are all related to one of the Microsoft Visual C++ Redistributable packages and can be ignored. I would suggest to try to update again.
 
This is interesting. I did the normal windows update, and this time it decided to go straight to 22h2 instead of 21h1. Must have something to do with the insider program?
 
Maybe, what is the result of the following command:
Code: 
reg query HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade
 
Ok well... Windows update said "this update can not be downloaded because it is not ready for your device"

I'll try media creation tool now
 
Could you please provide the following registry export first? Zip setup.hiv and attach it to your next post.

Code: 
reg save "HKEY_LOCAL_MACHINE\SYSTEM\Setup" "%userprofile%\Desktop\Setup.hiv"
 
Microsoft Windows [Version 10.0.19042.1165]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reg query HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade

HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\Appx
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\Bluetooth
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\Bridge
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\DoMp1_2
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\DoMp2_2
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\HDAudio
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\NetworkDriverBackup
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\PnP
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\TileDataModel
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\Unimodem
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\WinsockUpgrade
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Upgrade\WSearch

C:\WINDOWS\system32>
 
sure

Mod edit: attachement removed because it contains a private e-mailadres.
 
Last edited by a moderator:
Could you please perform a REG search for the following {clsid}.

Download the 64 bit version: - Farbar Recovery Scan Tool Link

  • Right-click on the file FRST64.exe and choose Run as administrator.
    • Copy and paste the following (code) into the Search box and click the Search Registry button.
    Code: 
    {C939EC0F-2F56-4CE8-AF56-2336596A5FA7}
    • When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
    • Post the logfile SearchReg.txt as attachment in your next reply.
 
Hmm, nothing found. P.s. I've removed the attachement from post #236 because of your private e-mailadres..
 
You must log in or register to reply here.
Back
Top