[SOLVED] Win10 - refuses to update to 22H2
- Thread starter dsalch
- Start date
In the meanwhile, I have sorted out some things to see what we can do, in anticipation of the expertise of the Academy Instructors.
I was doing a little amateur investigation and found some interesting points and questions (unless I am misinterpreting something)
1. The userdif file is only used when upgrading to manage user profiles during the upgrade
2. #1 would mean that this is not necessary for running, only for major upgrades
3. The registry seems ok, but the file is corrupt, so is it possible to recreate the file from the registry?
4. What will happen during upgrade if the file is missing? would it continue without, crash, or recreate?
5. When does this file get created? It must not be stock, and if #1 is correct, it would need to be created or at least updated when an upgrade is initiated (to make sure it's up to date) , so can that be forced?
6. this file seems to be a target for malware. I saw quite a few references to malware corrupting this particular file.
1. The userdif file is only used when upgrading to manage user profiles during the upgrade
2. #1 would mean that this is not necessary for running, only for major upgrades
3. The registry seems ok, but the file is corrupt, so is it possible to recreate the file from the registry?
4. What will happen during upgrade if the file is missing? would it continue without, crash, or recreate?
5. When does this file get created? It must not be stock, and if #1 is correct, it would need to be created or at least updated when an upgrade is initiated (to make sure it's up to date) , so can that be forced?
6. this file seems to be a target for malware. I saw quite a few references to malware corrupting this particular file.
Hi,
I will come back on your questions later, it seems we where able to rebuild the userdiff file.
1. Make a complete systemimage before performing the following steps.
2. Unzip the attached file and replace the userdiff file in C:\Windows\System32\Config
3. Reboot the system and attempt to update again.
I will come back on your questions later, it seems we where able to rebuild the userdiff file.
1. Make a complete systemimage before performing the following steps.
2. Unzip the attached file and replace the userdiff file in C:\Windows\System32\Config
3. Reboot the system and attempt to update again.
Ok. Update running. Fortunately I just made a full backup last night.
1. Indeed, and it seems this file only exists on systems with multiple user accounts.
2. I'm not sure, the last write timestamp on my own system was 2021, so I don't know exactly when it is needed during an update or not.
3. No, we have rebuilded the file with the information given in the logfiles.
4. I think it will fail if the file is missing.
5. I Don't know, this is the first time I've seen an issue with this file and couldn't find any similar issues in older threads. So I don't have an explanation for it.
6. That's right, I've noticed that too and your system was compromised in the past as well..
Was the option "download updates, drivers and optional features (recommended)" selected in the Media Creation tool, or the option Not right now?
For now I woudn't change anything, if it fails provide the setupact and setuperr logfiles first to look at.
For now I woudn't change anything, if it fails provide the setupact and setuperr logfiles first to look at.
Great!
You're welcome and glad to hear upgrade using MCT succeeded this time...
I would suggest the following:
1. Make a new full backup of the system.
2. Make seperate backups of the registry with Acelogix RegBak, this wil not include files like userdiff, so you'll need to backup such files manually. Before creating a backup with this tool, open the settings screen by clicking the option Click here to view details. I recommend to select the option (...) hives not loaded by Windows, and/or Others to create a full backup.
3. SFCFix, ComponentsScanner and logfiles can be removed manualy. FRST can be removed by renaming the file to Uninstall.exe.
Follow the instructions below to remove
FRST and all the log files.
You're welcome and glad to hear upgrade using MCT succeeded this time...
I would suggest the following:
1. Make a new full backup of the system.
2. Make seperate backups of the registry with Acelogix RegBak, this wil not include files like userdiff, so you'll need to backup such files manually. Before creating a backup with this tool, open the settings screen by clicking the option Click here to view details. I recommend to select the option (...) hives not loaded by Windows, and/or Others to create a full backup.
3. SFCFix, ComponentsScanner and logfiles can be removed manualy. FRST can be removed by renaming the file to Uninstall.exe.
Follow the instructions below to remove
- Rename the file FRST64.exe to uninstall.exe and run it as Administrator.
- This will remove all files and folders created by FRST and the tool itself.
- To complete this the system must be restart.
Last edited:
Update, the system went through a long string of updates through regular update process. Several reboots, and several hours later, windows update declares it all up to date. I'll start cleaning up now.
I do notice lots of new processes running, and responsiveness is noticeably slower. Must be new stuff they added. If all stays healthy for a bit I might try removing the extras.
I do notice lots of new processes running, and responsiveness is noticeably slower. Must be new stuff they added. If all stays healthy for a bit I might try removing the extras.
I would start with running Disk Cleanup (cleanmgr) if everything is up and running. And new features like news and interests can be disabled from the taskbar.
Hi.
Glad to here everything is up and running. You can only donate to Sysnative using PayPal or debit and creditcard.
Glad to here everything is up and running. You can only donate to Sysnative using PayPal or debit and creditcard.
Has Sysnative Forums helped you? Please consider donating to help us support the site!