SFCFix unhandled exception

M

mcquats

Member
Joined
Jul 17, 2020
Posts
11
After a recent windows 10 update and restart I've been unable to get into my profile. I've tried a few things in regedit and the SFC/DISM scan, but so far no luck. The SFCFix also gives an error right off the start.

Any help would be greatly appreciated.
 

Attachments

Hi mcquats

Apologies for the delay. Are you still requiring assistance?
 
ok

Will have a look over the logs and come back to you. :-)
 
Please do the following.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put </> tags around the log to break up the text.
 

Attachments

SFCFix successfully completed this time. Does that mean I'm good to go?

Should I now delete the temporary user profiles and rename rename my original profile to remove the .bak?

<
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-07-21 20:52:17.275
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\TEMP.NORBORD.000.001.002.003.004.005\Desktop\SFCFix.zip []


PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.json
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.txt
Successfully copied file C:\Users\TEMP.NORBORD.000.001.002.003.004.005\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.json to C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.json.
Successfully copied file C:\Users\TEMP.NORBORD.000.001.002.003.004.005\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.txt to C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.txt.
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.json
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.json
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.txt
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..userpredictionmodel_31bf3856ad364e35_10.0.17763.1_none_7d9e9b366f891397\SBCModel.txt
PowerCopy:: directive completed successfully.


Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2020-07-21 20:53:30.882
----------------------EOF--------------
>
 
Hi

No, don't change anything at the moment.

Please do the following.

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 
Hi

Please do the following.

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put </> tags around the log to break up the text.
 

Attachments

That ran through fast...

<
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-07-22 16:59:45.400
Microsoft Windows 10 Build 17763 - amd64
Using .zip script file at C:\Users\TEMP.NORBORD.000.001.002.003.004.005.006\Desktop\SFCFix.zip []


PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-u..access-userdataapis_31bf3856ad364e35_10.0.17763.1_none_faa3be93195c03e0\EmailApis.dll
Successfully copied file C:\Users\TEMP.NORBORD.000.001.002.003.004.005.006\AppData\Local\niemiro\Archive\amd64_microsoft-windows-u..access-userdataapis_31bf3856ad364e35_10.0.17763.1_none_faa3be93195c03e0\EmailApis.dll to C:\Windows\winsxs\amd64_microsoft-windows-u..access-userdataapis_31bf3856ad364e35_10.0.17763.1_none_faa3be93195c03e0\EmailApis.dll.
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-u..access-userdataapis_31bf3856ad364e35_10.0.17763.1_none_faa3be93195c03e0\EmailApis.dll
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-u..access-userdataapis_31bf3856ad364e35_10.0.17763.1_none_faa3be93195c03e0\EmailApis.dll
PowerCopy:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2020-07-22 16:59:45.759
----------------------EOF-----------------------
>
 
Please do the following.

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or OneDrive or SendSpace and just provide the link.
 
ok, can you try windows updates please and attach cbs log if it fails.
 
"We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet."

cbs.txt
 
ok, lets try a SFC scan

Please do the following.

SFC Scan
  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
    Note: If the file is too large to upload, use a file sharing service like Sendspace and paste the link here.
 
Should I restart? It seems to give me a new TEMP user profile each time I restart, so I've set the computer to not lock or sleep.
 
I created a new Local profile, which was a task in itself. Could only create one through Computer management.

I tried to install windows updates but it didn't work. Then I connected to my VPN (which wasn't working in the TEMP profile), and tried updates again. So fare it is downloading 4 updates... fingers crossed.

It must have been something with the connection settings???
 
Hi mcquats

Pleased to here you've got things going, albeit with a workaround.

Your logs look ok so I would think you should be able to get the updates.

The fact that your microsoft account and windows updates not connecting to the service does raise suspicions of a network connectivity issue.

This was an issue back at the beginning of 2019 for some folk which Microsoft claim is fixed. There is an article here on it from bleeping computer.

If your system has not updated for a while then hopefully you might get this fixed in the round of updates you are doing and things will be back to normal.

A temporary solution is to change the DNS servers to google (8.8.8.8) - this has worked for some and is explained in the article how to do this.

Let me know how you get on. :-)
 
You must log in or register to reply here.

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

Back
Top