[SOLVED] I cant get win 10 home to upgrade nor my regedit working

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Please run the FRST64 fix first, if it is successful, then please run the SFCFix fixes.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 05-02-2022
Ran by Mark (09-02-2022 09:53:26) Run:1
Running from C:\Download\AAA
Loaded Profiles: Mark
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
Reg: reg add HKLM\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-i..ibinaries.resources_31bf3856ad364e35_10.0.14393.0_en-us_2e854b5d00bdb3af /v f!iisfcgi.dll.mui /t REG_DWORD /d 0x21 /f
Reg: reg add HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..ibinaries.resources_31bf3856ad364e35_10.0.14393.0_en-us_2430a10acc5cf1b4 /v f!iisfcgi.dll.mui /t REG_DWORD /d 0x21 /f
*****************

Restore point was successfully created.

========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.



========= End of Reg: =========


========= reg add HKLM\COMPONENTS\DerivedData\Components\wow64_microsoft-windows-i..ibinaries.resources_31bf3856ad364e35_10.0.14393.0_en-us_2e854b5d00bdb3af /v f!iisfcgi.dll.mui /t REG_DWORD /d 0x21 /f =========

The operation completed successfully.



========= End of Reg: =========


========= reg add HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-i..ibinaries.resources_31bf3856ad364e35_10.0.14393.0_en-us_2430a10acc5cf1b4 /v f!iisfcgi.dll.mui /t REG_DWORD /d 0x21 /f =========

The operation completed successfully.



========= End of Reg: =========


==== End of Fixlog 09:53:43 ====
 
unfortunately same issues, your script it killed regedit again.
Sfc dies at 98% verification phase
 
The version in the SFCFix folder is the correct one, it has the same hashes it was expecting in the CBS log. Could you please provide the latest CBS log?
 
Rich (BB code):
2022-02-09 10:03:12, Info                  CSI    00001ab1 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-c..trast-black.cortana_31bf3856ad364e35_10.0.14393.0_none_a8182039d16660dc\AppListIcon.scale-100.png do not match actual file [l:25]'AppListIcon.scale-100.png' :
  Found: {l:32 6vvUWNNGjKBhcY5gjR2oJ5own9CEsHSEyIrfYtvqur4=} Expected: {l:32 pcTaQheLp/AF92VrFb37Fg/Xtt0fl+Rxq4R2LDICxIM=}
2022-02-09 10:03:12, Info                  CSI    00001ab2 [SR] Cannot repair member file [l:25]'AppListIcon.scale-100.png' of Microsoft-Windows-Cortana.Desktop.AppxMain.Assets.Icons.custom-Cortana.contrast-black.Cortana, version 10.0.14393.0, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-02-09 10:03:12, Info                  CSI    00001ab3 [SR] This component was referenced by [l:96]'Microsoft-Windows-Cortana-Package~31bf3856ad364e35~amd64~~10.0.14393.0.Microsoft-Windows-Cortana'
2022-02-09 10:03:12, Info                  CSI    00001ab4 Hashes for file member \??\C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\Assets\Icons\custom-Cortana\contrast-black\AppListIcon.scale-100.png do not match actual file [l:25]'AppListIcon.scale-100.png' :
  Found: {l:32 6vvUWNNGjKBhcY5gjR2oJ5own9CEsHSEyIrfYtvqur4=} Expected: {l:32 pcTaQheLp/AF92VrFb37Fg/Xtt0fl+Rxq4R2LDICxIM=}
2022-02-09 10:03:12, Info                  CSI    00001ab5 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-c..trast-black.cortana_31bf3856ad364e35_10.0.14393.0_none_a8182039d16660dc\AppListIcon.scale-100.png do not match actual file [l:25]'AppListIcon.scale-100.png' :
  Found: {l:32 6vvUWNNGjKBhcY5gjR2oJ5own9CEsHSEyIrfYtvqur4=} Expected: {l:32 pcTaQheLp/AF92VrFb37Fg/Xtt0fl+Rxq4R2LDICxIM=}


The same as before please.
 

Attachments

Hi unfortunately same problem, picture and logs attached. but regedit works ok ;)

thank you
 

Attachments

  • sfc2-10-2022.jpg
    sfc2-10-2022.jpg
    116.8 KB · Views: 2
  • CBS.zip
    CBS.zip
    4.9 MB · Views: 2
The only remaining corrupted file I can see is regedit.exe:

Rich (BB code):
2022-02-10 20:04:26, Info                  CSI    00003247 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-registry-editor_31bf3856ad364e35_10.0.14393.953_none_2df9ef4779cceca3\regedit.exe do not match actual file [l:11]'regedit.exe' :
  Found: {l:32 Htoo0Ru07G3nQbepMjsTWNk/eWeReZ94esViYRa0rLw=} Expected: {l:32 JUsYqMxlia9mbuF85OdsZzUK7PV4IGzHZ4dF7UejLWM=}
2022-02-10 20:04:26, Info                  CSI    00003248 [SR] Cannot repair member file [l:11]'regedit.exe' of Microsoft-Windows-Registry-Editor, version 10.0.14393.953, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2022-02-10 20:04:26, Info                  CSI    00003249 [SR] This component was referenced by [l:80]'Package_3065_for_KB4093119~31bf3856ad364e35~amd64~~10.0.1.5.4093119-6498_neutral'
2022-02-10 20:04:26, Info                  CSI    0000324a Hashes for file member \??\C:\Windows\regedit.exe do not match actual file [l:11]'regedit.exe' :
  Found: {l:32 Htoo0Ru07G3nQbepMjsTWNk/eWeReZ94esViYRa0rLw=} Expected: {l:32 JUsYqMxlia9mbuF85OdsZzUK7PV4IGzHZ4dF7UejLWM=}
2022-02-10 20:04:26, Info                  CSI    0000324b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-registry-editor_31bf3856ad364e35_10.0.14393.953_none_2df9ef4779cceca3\regedit.exe do not match actual file [l:11]'regedit.exe' :
  Found: {l:32 Htoo0Ru07G3nQbepMjsTWNk/eWeReZ94esViYRa0rLw=} Expected: {l:32 JUsYqMxlia9mbuF85OdsZzUK7PV4IGzHZ4dF7UejLWM=}
2022-02-10 20:04:26, Info                  CSI    0000324c [SR] Could not reproject corrupted file \??\C:\Windows\regedit.exe; source file in store is also corrupted

I'm going to provide you with a known good and correct copy again. Please then run SFC again and then provide the CBS log if it fails.

Please do not copy any files over from a different folder.
 

Attachments

Sorry for the hold up, I don't have the machine next to me, for now.

Picture and new log attached
 

Attachments

  • sfc 2-13-2022.jpg
    sfc 2-13-2022.jpg
    120.2 KB · Views: 1
  • CBS.zip
    CBS.zip
    3.1 MB · Views: 2
Rich (BB code):
2022-02-13 11:24:09, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(14098) #848636# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 21e5ea4c61b8bf7648942248960b3e21, version 10.0.14393.2214, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_8_for_KB4093120~31bf3856ad364e35~amd64~~10.0.1.4.4093120-23_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073712]
2022-02-13 11:24:09, Info                  CBS    Failed to pin deployment while staging Update: 4093120-23_neutral [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-02-13 11:24:09, Info                  CBS    Failed to stage item[0] in Package: Package_8_for_KB4093120~31bf3856ad364e35~amd64~~10.0.1.4, Update: 4093120-23_neutral [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-02-13 11:24:09, Info                  CBS    Failed to stage execution update for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2214.1.4 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-02-13 11:24:09, Info                  CSI    0000000d@2022/2/13:16:24:09.677 CSI Transaction @0x1281c2d4d50 destroyed
2022-02-13 11:24:09, Error                 CBS    Failed to pre- stage package, package: Package_8_for_KB4093120~31bf3856ad364e35~amd64~~10.0.1.4 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-02-13 11:24:09, Info                  CBS    CommitPackagesState: Started persisting state of packages
2022-02-13 11:24:09, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2022-02-13 11:24:09, Info                  CSI    0000000e@2022/2/13:16:24:09.745 CSI Transaction @0x1281c2d4720 destroyed

Install Update with DISM
  1. Download the update MSU here: KB4093120
  2. Copy the MSU file to a convenient location (such as %userprofile%\Desktop).
  3. Click on the Start button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. When command prompt opens, copy and paste the following commands into it, press enter after each

    cd %userprofile%\Desktop

    replace %userprofile%\Desktop with your path if different

    expand windows10.0-kb4093120-x64_72c7d6ce20eb42c0df760cd13a917bbc1e57c0b7.msu -f:* %userprofile%\Desktop

    DISM.exe /Online /Add-Package /PackagePath:%userprofile%\Desktop\Windows10.0-KB4093120-x64.cab
  6. You should receive the message:
    The operation completed successfully.
    Make sure to allow the computer to restart if prompted.
  7. If you receive any other message:
    Post a screenshot of the Command Prompt window.
    Zip and attach the file C:\Windows\Logs\CBS\CBS.log
 
It didn't work. the interesting thing is that I can run regedit and devmgmt.msc or anything else that dosent work from C:\windows\syswow64 folder
 

Attachments

  • CBS.zip
    CBS.zip
    3.3 MB · Views: 2
  • dism.log
    dism.log
    15.7 MB · Views: 1
  • DISM 2-16-2022.jpg
    DISM 2-16-2022.jpg
    115.9 KB · Views: 2
  • devmgmt 2-16-2022.jpg
    devmgmt 2-16-2022.jpg
    83.9 KB · Views: 2
  • working devmgmt from sysWOW64 2-16-2022.jpg
    working devmgmt from sysWOW64 2-16-2022.jpg
    121.4 KB · Views: 2
the interesting thing is that I can run regedit and devmgmt.msc or anything else that dosent work from C:\windows\syswow64 folder
Do you mean you can't or can? We'll look into those issues afterwards, let's focus on resolving these update issues first of all.

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4093120 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Hey, so since last Wednesday I can get the computer to bootup. It freezes (spinning cercle) a few seconds after bootup and then I get BSOD 0xc0000001.
Spent all weekend trying to get it back up to no avail. I tried to get into safe mode and also only get a black screen with a mouse pointer and nothing else :(
 
That's not an BSOD bugcheck code, it'll be related to something with your Windows installation. Do you have access to another working computer? You could attempt to perform an in-place upgrade to repair the operating system.
 
I can use your advice. I tried everything. I tried booting from a flash drive and running sfc and dism. SFC stops att 100% intergrity check and dism gives me error 193.
Please advie :(
 
Please boot from the USB flash drive, navigate to the CBS folder and then copy over the CBS log files to your USB flash drive. Afterwards, please attach them to your next post.

Rich (BB code):
%systemroot%\Logs\CBS

Addendum:

You may also want to add the DISM log which can be found in the following location:

Rich (BB code):
%systemroot%\Logs\DISM
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top