[SOLVED] Corrupted files

A

alize00

Contributor
Joined
Jan 8, 2016
Posts
20
Location
France
Hello,
The trouble starts when trying to update to Windows 10.
The result is always the error x80070050

I ran all possible things find on the net from Microsoft Fixit system to many other

For short, the main tools :
- sfc /scannow (100 times) including from install DVD with option /offbootdir and /offwindir
- Dism /Online /Cleanup-Image /CheckHealth
- sfcfix.exe
- sfcfix.zip over sfcfix.exe

Still remaining one problem related to GPEDIT program that has been tried months ago
None of the above could repair corrupted files has they are not part of standard windows 7 family edition running on the machine

You will find attache a zip file including SFCfix.txt together with the [SR] line of CBS.log

Thanks in advance for your help
Francis
 

Attachments

Hi and welcome to Sysnative. Let's see what we can do. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  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

Step#2 - SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    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.

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Items for your next post
1. SFCFix.txt
2. CBS.txt
 

Attachments

Hi Brian
Thank you very much for your assistance and quick reply

Please find below copy of the SFCfix.txt

SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-10 05:11:48.410
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.


AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 20
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 26
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2016-01-10 05:12:15.866

Attached the CBS.log in Zip format
 

Attachments

It doesn't appear Step#1 worked properly. Did you ensure that you dragged and dropped SFCFix.zip over the top of SFCFix.exe?

JQLRgtF.gif
 
Hi Brian,

I just drag it again then sfc /scannow again

Here are the results

SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-11 16:31:08.327
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\FS\Desktop\SFCFix.zip [1]

PowerCopy::
Successfully took permissions for file or folder C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_063200e5724abc1a\fde.dll
Successfully took permissions for file or folder C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_3ddb97ac675ddf20\fdeploy.dll

WARNING: File C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll was not backed up as that would replace the current backup.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll to C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_063200e5724abc1a\fde.dll to C:\Windows\Winsxs\amd64_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_063200e5724abc1a\fde.dll.
WARNING: File C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_3ddb97ac675ddf20\fdeploy.dll was not backed up as that would replace the current backup.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_3ddb97ac675ddf20\fdeploy.dll to C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_3ddb97ac675ddf20\fdeploy.dll.

Successfully restored ownership for C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully restored permissions on C:\Windows\Winsxs\x86_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_e1bcfc28af006dea\fdeploy.dll
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_063200e5724abc1a\fde.dll
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-fde_31bf3856ad364e35_6.1.7601.17514_none_063200e5724abc1a\fde.dll
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_3ddb97ac675ddf20\fdeploy.dll
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy_31bf3856ad364e35_6.1.7601.17514_none_3ddb97ac675ddf20\fdeploy.dll
PowerCopy:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 10 datablocks.
Finish time: 2016-01-11 16:31:08.752
Script hash: 45WXI/1lKC/dEGIe4twEzJnn4TW4t05g7iMh6hsvWVM=

You will find both result in the zip file attached
Thank you to spend time to help me

Best regards
Francis
 

Attachments

Thanks. There are more fixes to make. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  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


Step#2 - SFC Scan

  1. Click on the Start
    Start%20Orb.jpg
    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.


Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Items for your next post
1. SFCFix.txt
2. CBS.txt
 

Attachments

Hi Brian,

Things seems to be a lot better now as shown here-under

SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-12 06:32:57.344
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 19
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 13 datablocks.
Finish time: 2016-01-12 06:33:08.186

The CBS log file still indicates language fr-fr missing files (please see attached Zip file)

You already solve a lot of major errors
icon6.png

 

Attachments

Thanks. Please do the following now.

Step#2 - SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    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.



Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Please find attached the requested cbs log
For your information Windows6.1-KB947821-v34-x64.msu has been run early this morning
Checksur.log should be up to date so far

Thank for to be so patient
 

Attachments

No problem. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  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
 

Attachments

Good morning Brian,

The latest fix.zip was successfully applied

Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_server-help-chm.gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_abce2f2a317ddb73\gpedit.CHM to C:\Windows\Winsxs\amd64_server-help-chm.gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_abce2f2a317ddb73\gpedit.CHM.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_03a64131170229c8\gpedit.dll.mui to C:\Windows\Winsxs\amd64_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_03a64131170229c8\gpedit.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_c10638e28df836c9\gptext.dll.mui to C:\Windows\Winsxs\amd64_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_c10638e28df836c9\gptext.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_0c122cfc48d72590\fdeploy.dll.mui to C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_0c122cfc48d72590\fdeploy.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_8cff405e05768c66\fde.dll.mui to C:\Windows\Winsxs\amd64_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_8cff405e05768c66\fde.dll.mui.

Successfully restored ownership for C:\Windows\Winsxs\amd64_server-help-chm.gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_abce2f2a317ddb73
Successfully restored permissions on C:\Windows\Winsxs\amd64_server-help-chm.gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_abce2f2a317ddb73
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_03a64131170229c8
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_03a64131170229c8
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_c10638e28df836c9
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_c10638e28df836c9
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_0c122cfc48d72590
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_0c122cfc48d72590
Successfully restored ownership for C:\Windows\Winsxs\amd64_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_8cff405e05768c66
Successfully restored permissions on C:\Windows\Winsxs\amd64_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_8cff405e05768c66
PowerCopy:: directive completed successfully.
 
Latest news
This morning, to ensure an update of the checksur.log, I ran once again the KB947821
The SFCfix.txt confirm that
AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 10
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0

10 files are still missing as following in checksur.log file


Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Payload File Missing 0x00000000 fde.dll.mui x86_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_30e0a4da4d191b30
(f) CSI Payload File Missing 0x00000000 gpedit.dll.mui x86_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a787a5ad5ea4b892
(f) CSI Payload File Missing 0x00000000 fdeploy.dll.mui x86_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_aff391789079b45a
(f) CSI Payload File Missing 0x00000000 gptext.dll.mui x86_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_64e79d5ed59ac593
(f) CSI Payload File Missing 0x00000000 rsop.msc x86_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_70b8f4d5d896589c
(f) CSI Payload File Missing 0x00000000 gpedit.msc x86_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_70b8f4d5d896589c
(f) CSI Payload File Missing 0x00000000 rsop.msc amd64_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_ccd7905990f3c9d2
(f) CSI Payload File Missing 0x00000000 gpedit.msc amd64_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_ccd7905990f3c9d2
(f) CSI Payload File Missing 0x00000000 gpedit.msc amd64_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a957712fdcff0cae
(f) CSI Payload File Missing 0x00000000 gpedit.msc x86_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_4d38d5ac24a19b78

Summary:
Seconds executed: 180
Found 10 errors
CSI Payload File Missing Total count: 10


 
Thanks for the info. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  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
 

Attachments

Hi Brian
Updated successfully as shown below (SFCfix.txt extract)

Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_4d38d5ac24a19b78\gpedit.msc to C:\Windows\Winsxs\x86_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_4d38d5ac24a19b78\gpedit.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_4d38d5ac24a19b78\rsop.msc to C:\Windows\Winsxs\x86_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_4d38d5ac24a19b78\rsop.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a787a5ad5ea4b892\gpedit.dll.mui to C:\Windows\Winsxs\x86_microsoft-windows-g..in-gpedit.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a787a5ad5ea4b892\gpedit.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_64e79d5ed59ac593\gptext.dll.mui to C:\Windows\Winsxs\x86_microsoft-windows-g..cy-gptext.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_64e79d5ed59ac593\gptext.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_70b8f4d5d896589c\gpedit.msc to C:\Windows\Winsxs\x86_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_70b8f4d5d896589c\gpedit.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_70b8f4d5d896589c\rsop.msc to C:\Windows\Winsxs\x86_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_70b8f4d5d896589c\rsop.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_aff391789079b45a\fdeploy.dll.mui to C:\Windows\Winsxs\x86_microsoft-windows-fdeploy.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_aff391789079b45a\fdeploy.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\x86_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_30e0a4da4d191b30\fde.dll.mui to C:\Windows\Winsxs\x86_microsoft-windows-fde.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_30e0a4da4d191b30\fde.dll.mui.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a957712fdcff0cae\gpedit.msc to C:\Windows\Winsxs\amd64_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a957712fdcff0cae\gpedit.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a957712fdcff0cae\rsop.msc to C:\Windows\Winsxs\amd64_microsoft-windows-g..it-snapin.resources_31bf3856ad364e35_6.1.7600.16385_fr-fr_a957712fdcff0cae\rsop.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_ccd7905990f3c9d2\gpedit.msc to C:\Windows\Winsxs\amd64_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_ccd7905990f3c9d2\gpedit.msc.
Successfully copied file C:\Users\FS\AppData\Local\niemiro\Archive\Winsxs\amd64_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_ccd7905990f3c9d2\rsop.msc to C:\Windows\Winsxs\amd64_microsoft-windows-g..admin-gpedit-snapin_31bf3856ad364e35_6.1.7600.16385_none_ccd7905990f3c9d2\rsop.msc.
 
Total respect Brian for your knowledge and the quality of the assistance

Last SFC /scannow reports no error
checkSUR.log latest as below

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-13 16:42

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 210
No errors detected
 
I understand you are still having issues upgrading to Windows 10. Please start with the following.

Step#1 - Run Windows Repairs
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 Windows Repair (All-in-One) Portable to your desktop.
2. Once the file is downloaded, right-click on the file on your desktop and choose Extract All...
Extract.JPG

3. Keep the defaults and click the Extract button.
4. A folder named tweaking.com_windows_repair_aio will be extracted to the desktop. Once the extraction is complete the folder will open.
5. Inside this folder, there is a folder named Tweaking.com - Windows Repair. Open this folder as well.
Capture.JPG



6. Double-click on Repair_Windows.exe to open. Note: Please make sure all of your programs are closed and anything you were working on is saved as we will be rebooting.
7. When the program opens, click the Reboot to Safe Mode button at the bottom of the screen. Answer Yes to allow.
8. Once rebooted into Safe Mode, open the program again. When the program opens, click the Repairs tab and click the Open Repairs button.
9. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
10. Keep all the defaults

11. Ensure the Restart check box is selected and click the Start Repairs button in the lower right of the screen. This may take some time to run so be patient.
StartRepairsWithReboot.JPG

12. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.
 
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