Unable to update w10 home

bruce1270 · Jan 24, 2020

Hi spicypepperpasta

Apologies for the lengthy delay in replying, I have been trying to source a specific registry key.

Please do the following.

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
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.
Download attached file 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).
Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
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.
When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Spicypepperpasta · Jan 24, 2020

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 22-01-2020 01
Ran by nlam1 (25-01-2020 10:10:13) Run:1
Running from C:\Users\nlam1\Desktop
Loaded Profiles: nlam1 (Available Profiles: nlam1)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
reg: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

StartRegedit:

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.267_ja-jp_e2270ca202e2c2f9]
"S256H"=hex:0d,b8,8a,2f,52,78,43,0a,ae,32,bf,64,29,a7,c5,ca,92,ca,1d,9b,5e,97,\
  0a,1b,5d,77,b6,a3,57,14,9a,2e
"identity"=hex:6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,63,6c,69,\
  65,6e,74,2d,66,65,61,74,75,72,65,73,2d,64,65,70,6c,6f,79,6d,65,6e,74,30,2c,\
  20,43,75,6c,74,75,72,65,3d,6a,61,2d,4a,50,2c,20,56,65,72,73,69,6f,6e,3d,31,\
  30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2c,20,50,75,62,6c,69,63,4b,65,79,54,\
  6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,\
  6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,\
  2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"CF"=dword:0000000c
"c!microsoft-w..deployment0_31bf3856ad364e35_10.0.18362.267_e2270ca202e2c2f9"=hex:

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..deployment0_31bf3856ad364e35_10.0.18362.267_e2270ca202e2c2f9]
"appid"=hex:6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,63,6c,69,65,\
  6e,74,2d,66,65,61,74,75,72,65,73,2d,64,65,70,6c,6f,79,6d,65,6e,74,30,2c,20,\
  43,75,6c,74,75,72,65,3d,6a,61,2d,4a,50,2c,20,56,65,72,73,69,6f,6e,3d,31,30,\
  2e,30,2e,31,38,33,36,32,2e,32,36,37,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,\
  6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,\
  63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,\
  20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"CatalogThumbprint"="fa461e6bb62ce17f53426d255aa0e0154a790147536605f190fb455ecefc68ec"
"p!CBS_microsoft-windows-client-features-package~31bf3856ad364e35~a_142eaf57940310c2"=hex:96,\
  00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
  43,6c,69,65,6e,74,2d,46,65,61,74,75,72,65,73,2d,50,61,63,6b,61,67,65,7e,33,\
  31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,36,34,7e,6a,61,2d,\
  4a,50,7e,31,30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2e,34,38,41,39,42,41,43,\
  34,42,32,41,36,34,34,44,45,42,41,42,32,38,31,39,31,32,32,32,36,41,35,34,41,\
  37,38,44,34,45,43,38,44,32,38,43,37,39,42,32,42,44,43,32,31,46,37,35,33,36,\
  41,41,38,31,33,31,35
"s!CBS_microsoft-windows-client-features-package~31bf3856ad364e35~a_142eaf57940310c2"=hex:96,\
  00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
  43,6c,69,65,6e,74,2d,46,65,61,74,75,72,65,73,2d,50,61,63,6b,61,67,65,7e,33,\
  31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,36,34,7e,6a,61,2d,\
  4a,50,7e,31,30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2e,34,38,41,39,42,41,43,\
  34,42,32,41,36,34,34,44,45,42,41,42,32,38,31,39,31,32,32,32,36,41,35,34,41,\
  37,38,44,34,45,43,38,44,32,38,43,37,39,42,32,42,44,43,32,31,46,37,35,33,36,\
  41,41,38,31,33,31,35
"i!CBS_microsoft-windows-client-features-package~31bf3856ad364e35~a_142eaf57940310c2"=hex:96,\
  00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
  43,6c,69,65,6e,74,2d,46,65,61,74,75,72,65,73,2d,50,61,63,6b,61,67,65,7e,33,\
  31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,36,34,7e,6a,61,2d,\
  4a,50,7e,31,30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2e,34,38,41,39,42,41,43,\
  34,42,32,41,36,34,34,44,45,42,41,42,32,38,31,39,31,32,32,32,36,41,35,34,41,\
  37,38,44,34,45,43,38,44,32,38,43,37,39,42,32,42,44,43,32,31,46,37,35,33,36,\
  41,41,38,31,33,31,35

EndRegedit:
*****************

Restore point was successfully created.

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

The operation completed successfully.



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

Registry ====> The operation completed successfully.


==== End of Fixlog 10:10:30 ====

bruce1270 · Jan 24, 2020

Hi

please do the following.

Step#1 - Capture Process Monitor Trace

1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
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.

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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

Spicypepperpasta · Jan 24, 2020

CBS.zip
Logfile.zip

bruce1270 · Jan 26, 2020

Hi

Please do the following.

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
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.
Download attached file 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).
Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
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.
When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Spicypepperpasta · Jan 26, 2020

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 26-01-2020
Ran by nlam1 (26-01-2020 22:08:34) Run:2
Running from C:\Users\nlam1\Desktop
Loaded Profiles: nlam1 (Available Profiles: nlam1)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
reg: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

[-HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.267_ja-jp_e2270ca202e2c2f9]

[-HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..deployment0_31bf3856ad364e35_10.0.18362.267_e2270ca202e2c2f9]

StartRegedit:

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.267_ja-jp_e2270ca202e2c2f9]
"S256H"=hex:0d,b8,8a,2f,52,78,43,0a,ae,32,bf,64,29,a7,c5,ca,92,ca,1d,9b,5e,97,\
  0a,1b,5d,77,b6,a3,57,14,9a,2e
"identity"=hex:6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,63,6c,69,\
  65,6e,74,2d,66,65,61,74,75,72,65,73,2d,64,65,70,6c,6f,79,6d,65,6e,74,30,2c,\
  20,43,75,6c,74,75,72,65,3d,6a,61,2d,4a,50,2c,20,56,65,72,73,69,6f,6e,3d,31,\
  30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2c,20,50,75,62,6c,69,63,4b,65,79,54,\
  6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,\
  6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,\
  2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"CF"=dword:0000000c
"c!microsoft-w..deployment0_31bf3856ad364e35_10.0.18362.267_e2270ca202e2c2f9"=hex:

[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..deployment0_31bf3856ad364e35_10.0.18362.267_e2270ca202e2c2f9]
"appid"=hex:6d,69,63,72,6f,73,6f,66,74,2d,77,69,6e,64,6f,77,73,2d,63,6c,69,65,\
  6e,74,2d,66,65,61,74,75,72,65,73,2d,64,65,70,6c,6f,79,6d,65,6e,74,30,2c,20,\
  43,75,6c,74,75,72,65,3d,6a,61,2d,4a,50,2c,20,56,65,72,73,69,6f,6e,3d,31,30,\
  2e,30,2e,31,38,33,36,32,2e,32,36,37,2c,20,50,75,62,6c,69,63,4b,65,79,54,6f,\
  6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,72,6f,\
  63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,34,2c,\
  20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"CatalogThumbprint"="fa461e6bb62ce17f53426d255aa0e0154a790147536605f190fb455ecefc68ec"
"p!CBS_microsoft-windows-client-features-package~31bf3856ad364e35~a_142eaf57940310c2"=hex:96,\
  00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
  43,6c,69,65,6e,74,2d,46,65,61,74,75,72,65,73,2d,50,61,63,6b,61,67,65,7e,33,\
  31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,36,34,7e,6a,61,2d,\
  4a,50,7e,31,30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2e,34,38,41,39,42,41,43,\
  34,42,32,41,36,34,34,44,45,42,41,42,32,38,31,39,31,32,32,32,36,41,35,34,41,\
  37,38,44,34,45,43,38,44,32,38,43,37,39,42,32,42,44,43,32,31,46,37,35,33,36,\
  41,41,38,31,33,31,35
"s!CBS_microsoft-windows-client-features-package~31bf3856ad364e35~a_142eaf57940310c2"=hex:96,\
  00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
  43,6c,69,65,6e,74,2d,46,65,61,74,75,72,65,73,2d,50,61,63,6b,61,67,65,7e,33,\
  31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,36,34,7e,6a,61,2d,\
  4a,50,7e,31,30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2e,34,38,41,39,42,41,43,\
  34,42,32,41,36,34,34,44,45,42,41,42,32,38,31,39,31,32,32,32,36,41,35,34,41,\
  37,38,44,34,45,43,38,44,32,38,43,37,39,42,32,42,44,43,32,31,46,37,35,33,36,\
  41,41,38,31,33,31,35
"i!CBS_microsoft-windows-client-features-package~31bf3856ad364e35~a_142eaf57940310c2"=hex:96,\
  00,00,00,00,00,00,00,4d,69,63,72,6f,73,6f,66,74,2d,57,69,6e,64,6f,77,73,2d,\
  43,6c,69,65,6e,74,2d,46,65,61,74,75,72,65,73,2d,50,61,63,6b,61,67,65,7e,33,\
  31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,64,36,34,7e,6a,61,2d,\
  4a,50,7e,31,30,2e,30,2e,31,38,33,36,32,2e,32,36,37,2e,34,38,41,39,42,41,43,\
  34,42,32,41,36,34,34,44,45,42,41,42,32,38,31,39,31,32,32,32,36,41,35,34,41,\
  37,38,44,34,45,43,38,44,32,38,43,37,39,42,32,42,44,43,32,31,46,37,35,33,36,\
  41,41,38,31,33,31,35

EndRegedit:
*****************

Restore point was successfully created.

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

The operation completed successfully.



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

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..eatures-deployment0_31bf3856ad364e35_10.0.18362.267_ja-jp_e2270ca202e2c2f9 => removed successfully
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-w..deployment0_31bf3856ad364e35_10.0.18362.267_e2270ca202e2c2f9 => removed successfully
Registry ====> The operation completed successfully.


==== End of Fixlog 22:08:43 ====

bruce1270 · Jan 26, 2020

Hi

please do the following.

Step#1 - Capture Process Monitor Trace

1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
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.

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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

Spicypepperpasta · Jan 27, 2020

CBS.zip
Logfile.zip

bruce1270 · Jan 28, 2020

Hi

Please do the following

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
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.
Download attached file 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).
Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
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.
When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

Spicypepperpasta · Jan 28, 2020

Code:

Restore point was successfully created.

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

The operation completed successfully.



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

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-client-li..oyment-languagepack_31bf3856ad364e35_10.0.18362.1_ja-jp_74d38aaefe682f4e => not found
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\microsoft-c..anguagepack_31bf3856ad364e35_10.0.18362.1_74d38aaefe682f4e => not found
Registry ====> The operation completed successfully.


==== End of Fixlog 08:21:30 ====

bruce1270 · Jan 28, 2020

Hi

please do the following.

Step#1 - Capture Process Monitor Trace

1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
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.

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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.

Spicypepperpasta · Jan 28, 2020

Slightly different situation here. Two new updates were available this time. While the process is probably listed in the cbs file, I'll just be explicit just in case. Summary is shown in the screencap provided.
1. First the .NET framework update was downloaded.
2. Then the old update we've been having trouble all this time failed to update once again.
3. Then the .NET framework update was successfully installed. There was a restart. (The first logfile will detail steps 1-3, or 2-3)
4. A new optional update became available and I clicked on that.
5. Failed to update. (2nd logfile will detail what happened.)

Downloads.zip
CBS.zip

I realise this is an iterative process so it might take a few tries to get this right, but I was wondering if the end is in sight. Thanks for all your help so far.

bruce1270 · Feb 2, 2020

Hi spicypepperpasta

I haven't forgotten about you, life's got in the way a bit but I am working on my next fix for you.

Apologies for the delay and thank you for your patience.

bruce1270 · Feb 3, 2020

Hi

Once again apologies for the delay.

I have a couple of questions.

1. Do you have any additional or extra features installed on your system?

2. Have you had a Japanese language pack or similar installed at any time?

Spicypepperpasta · Feb 4, 2020

bruce1270 said:
Hi

Once again apologies for the delay.

I have a couple of questions.

1. Do you have any additional or extra features installed on your system?

2. Have you had a Japanese language pack or similar installed at any time?

1. Don't think so. How can I tell?
2. I believe I have. Pretty sure I installed the japanese language pack and maybe the vietnamese language pack back when I first built the PC. I uninstalled them since it was messing with various warning screens.

bruce1270 · Feb 5, 2020

Hi

Please do the following.

1. Open an elevated command prompt.
2. At the command prompt type lpksetup and press enter.
3. Choose the option Uninstall display languages.
4. If Japanese is listed, please check it and follow the on screen instructions to uninstall it.
5. Please then reboot the system.

Spicypepperpasta · Feb 5, 2020

Uninstall failed. Then I installed a new pack from Settings and tried uninstalling again. Uninstall failed. Then I tried to install from lpksetup - don't know where to find the language pack.

bruce1270 · Feb 5, 2020

Hi

Please do the following.

Step#1 - Capture Process Monitor Trace

1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try to uninstall the Japanese language pack using lpksetup just like you have in the past.
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.

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 provide the link to the LogFile.PML file. Examples of services to upload to are Dropbox or OneDrive or SendSpace.

Spicypepperpasta · Feb 6, 2020

Logfile.zip

Spicypepperpasta · Feb 6, 2020

Out of curiosity (and frustration), I did a random dism and sfc check. Results have been different than they were a month ago. Still not fixed though, but might be worth looking at.

dism.log
CBS.log

Edit: Tried using sfcfix. Crashed right away. It uploaded something to your servers.

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-02-06 21:06:02.346
Microsoft Windows 10 Build 18362 - amd64
Not using a script file.




SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 769 datablocks.
Finish time: 2020-02-06 21:06:06.039
----------------------EOF-----------------------

Unable to update w10 home

Moderator, Windows Update Analyst, Security Analyst

Attachments

Active member

Moderator, Windows Update Analyst, Security Analyst

Active member

Moderator, Windows Update Analyst, Security Analyst

Attachments

Active member

Moderator, Windows Update Analyst, Security Analyst

Active member

Moderator, Windows Update Analyst, Security Analyst

Attachments

Active member

Moderator, Windows Update Analyst, Security Analyst

Active member

Attachments

Moderator, Windows Update Analyst, Security Analyst

Moderator, Windows Update Analyst, Security Analyst

Active member

Moderator, Windows Update Analyst, Security Analyst

Active member

Moderator, Windows Update Analyst, Security Analyst

Active member

Active member