Windows update couldn't install

[JoeRain]

Here you go

 

[Gary R]

From what I can see, I think the most likely "culprit" for the "Update" is ...

HKLM-x32\...\Run: [TeamsMachineUninstallerLocalAppData] => C:\Users\asus\AppData\Local\Microsoft\Teams\Update.exe [2492168 2022-05-18] (Microsoft 3rd Party Application Component -> Microsoft Corporation)
HKLM-x32\...\Run: [TeamsMachineUninstallerProgramData] => %ProgramData%\Microsoft\Teams\Update.exe --uninstall --msiUninstall --source=default (No File)

.... so nothing to worry about.

Working through your latest CBS.log, back when I've finished doing that.

 

[Gary R]

Can you please do the following ...

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• The file will likely be too large to upload here so please upload to a file sharing service.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

Can you also do the following ...

• Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator
• When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

• Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.)
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
• Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
• Attach the .ZIP file to your next post.
• If the file is too large to upload here, please upload to a file sharing service.
• Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file

 

[JoeRain]

Hello, Gary.

For the first file, I found 2 similar folders (pic attached). Am i meant to open the "config" one? Since I'm denied permission to access "Configuration" and the security tab showed that it's "unable to display current owner." If so, I attach it via gdrive.
COMPONENTS.zip

As for the registry hive file, the original size of the file is only 3,41 mb so I attach it via gdrive.
ComponentBasedServicing.zip

 

[Gary R]

OK, got your files, I'm going to need to load them into a Virtual Machine with the same version of W10 as you have before I can look through them, so this may take me a while to set up and process. Will get back to you as soon as possible.

 

[JoeRain]

Okay. Thank you so much. Hope everything will go well.

 

[Gary R]

Sorry for the long delay.

OK, before we go any further I've got a few questions to ask ....

• 1st .... is your computer dual-boot or single-boot ?
• 2nd .... do you have a Windows Installation/Repair disk available ?
• 3rd .... do you know how to create a System Image, using either Windows in built tools, or a 3rd party program like Macrium Reflect ?

 

[JoeRain]

Hello, Gary. Thank you so much for staying with me.

1. I guess it's single boot? Windows is the only OS
2. No. Do i have to create one? Will it be via a USB drive?
3. No. Though i have Macrium on my PC, it was only because i read that it could help with creating system image but i totally have no idea how.

 

[Gary R]

1. Single boot is what I expected.

2. It's probably a good idea to create one, just in case what we're going to do goes wrong (I don't expect it to, but I always like to have a recovery plan in place) to create one. The following article describes how to create one ... Create a recovery drive ... you'll need a USB drive of at least 16GB for W10.

3. If you want to make an image with Macrium, the following article describes how ... How to use Macrium Reflect to create an image of your PC hard drive ... as you already have it installed, scroll down to the section titled ... How to image your hard drive

If you'd prefer to make an image using Windows inbuilt tools, the following article describes how ... https://answers.microsoft.com/en-us...ndows-10/84fa6683-e3ac-4e93-9139-368af9267869

In both options above, you'll want to save your System Image to an external drive. If you don't have one, then a System Image is not entirely essential to us being able to proceed, it's just me being cautious, but it does give us the best possible recovery option if something untoward does happen, and with any potentially "unstable" system that eventuality is always a possibility.

Please create a Repair Disk/Drive (Recovery Drive) and a System Image, and let me know when you've done so, or if you have any problems.

 

[JoeRain]

Good day, Gary.

1. I think i have the recovery drive ready but just want to make sure if this is everything and there's no component missing (pic attached). I used MRM to build it.
2. I also want to make sure if it's correct to mark all these options to start the system image (they're all marked by default, pic attached).

 

[Gary R]

Yes, looks good.

If you used the default options, then you're pretty much sure to have created a usable image.

If you're in any doubt about whether you've followed the correct procedure, then the following article steps through the process, and should be easy to follow.


https://www.tenforums.com/tutorials/61026-backup-restore-macrium-reflect.html


So if you've created your Macrium Reflect Rescue Media, then we should be ready to go.

I'll wait to hear from you that you're happy to proceed, before posting my next set of instructions.

 

[JoeRain]

Gary, I just ran into a problem while trying to create the system image. I'm sure I followed all the steps from that site so I don't know what caused this.

 

[Gary R]

No idea why it's failed, and the error code 0x8004230f doesn't really give us any real help either.

# for hex 0x8004230f / decimal -2147212529
VSS_E_UNEXPECTED_PROVIDER_ERROR vsserror.h
# The shadow copy provider had an unexpected error while
# trying to process the specified operation.
# 1 matches found for "0x8004230f"

I suggest you try again with Macrium, and if it fails again, then I propose that you create a System Image and recovery drive using Windows inbuilt tools.

I'll describe how to do that if you decide to go down that route.

 

[JoeRain]

Yes okay. Do I need to replace MRM too with the one from Windows?

Edit: should I just follow the instruction you gave on post #69?

 

[JoeRain]

Gary, I just tried creating a recovery drive and it said there was an error. Same with System Image. Guess I can't really do anything to back up this PC.

 

[Gary R]

OK, let's see if your Volume Shadow Service is running ....

Download FRST64 to your Desktop.

• Start FRST.
• Hit your Windows Key + R to open a Run window
• Type Notepad then click OK
• This will open an empty Notepad document
• Copy/Paste the following into it (Don't include Code: ) .....

cmd:sc query VSS
cmd:sc qc VSS

• Save it as fixlist.txt to the same location as FRST (must be in this location)
• NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
• Now press the Fix button once and wait.
• FRST will process fixlist.txt
• When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
• Please post me the log

 

[JoeRain]

Ok, here you go. Hopefully not another problem....

Fix result of Farbar Recovery Scan Tool (x64) Version: 14-06-2022
Ran by asus (15-06-2022 21:42:14) Run:2
Running from C:\Users\asus\Desktop
Loaded Profiles: asus
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd:sc query VSS
cmd:sc qc VSS
*****************


========= sc query VSS =========


SERVICE_NAME: VSS
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0


========= End of CMD: =========


========= sc qc VSS =========

[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: VSS
TYPE : 10 WIN32_OWN_PROCESS
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : C:\Windows\system32\vssvc.exe
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : Volume Shadow Copy
DEPENDENCIES : RPCSS
SERVICE_START_NAME : LocalSystem


========= End of CMD: =========


==== End of Fixlog 21:42:15 ====

 

[Gary R]

OK, as far as I can see, that looks as it should.

Please do the following ...

• Start FRST.
• Hit your Windows Key + R to open a Run window
• Type Notepad then click OK
• This will open an empty Notepad document
• Copy/Paste the following into it (Don't include Code: ) .....

cmd:sc config VSS start=auto
cmd:sc  start VSS

• Save it as fixlist.txt to the same location as FRST (must be in this location)
• NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
• Now press the Fix button once and wait.
• FRST will process fixlist.txt
• When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
• Please post me the log

Now try again to create a System Image using Windows inbuilt tools ... Redirecting

Let me know if successful, or if not post any error messages you may get

 

[JoeRain]

Here's the log

Fix result of Farbar Recovery Scan Tool (x64) Version: 16-06-2022
Ran by asus (16-06-2022 20:32:03) Run:3
Running from C:\Users\asus\Desktop
Loaded Profiles: asus
Boot Mode: Normal
==============================================

fixlist content:
*****************
cmd:sc config VSS start=auto
cmd:sc start VSS
*****************


========= sc config VSS start=auto =========

[SC] ChangeServiceConfig SUCCESS


========= End of CMD: =========


========= sc start VSS =========


SERVICE_NAME: VSS
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 11796
FLAGS :


========= End of CMD: =========


==== End of Fixlog 20:32:04 ====


Despite this, system image still failed. Or maybe I should restart the PC after running the fix?

 

[Gary R]

No, doesn't need a restart.

OK, first let's set VSS back to the way it was.

Please do the following ...

• Start FRST.
• Hit your Windows Key + R to open a Run window
• Type Notepad then click OK
• This will open an empty Notepad document
• Copy/Paste the following into it (Don't include Code: ) .....

cmd:sc config VSS start=manual
cmd:sc  stop VSS

• Save it as fixlist.txt to the same location as FRST (must be in this location)
• NOTICE: This script was written specifically for this user. Running it on another machine may cause damage to your operating system
• Now press the Fix button once and wait.
• FRST will process fixlist.txt
• When finished, it will produce a log fixlog.txt in the same folder/directory as FRST64.exe
• Please post me the log

Next ...



We need to run some tests on your memory and hard drive, to check whether they are "sound" or not.

• Please run MemTest86 for at least 8 passes (will require two runs) - Test RAM with PassMark MemTest86
• Please run a Hard Drive Diagnostic with Sea Tools - Hard Drive (HDD) Diagnostics (Sea Tools for DOS) & SSD Test

Let me know the results