[SOLVED] [10v1703b15063 x64] Diagnostic tools stopped working. Upd. (v1709b16299) didn't help.

Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

sorry, was occupied over the weekend. Here is View attachment dberr.txt.

I will now proceed to see if I can execute the fix you last posted. Will let you know once done. Cheers -
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Code: 
[/COLOR]SFCFix version 3.0.0.0 by niemiro.Start time: 2017-12-04 21:31:14.800
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\LX\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Cleanup.xml
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Generalize.xml
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Respecialize.xml
Successfully took permissions for file or folder C:\Windows\Sysnative\Sysprep\ActionFiles\Specialize.xml


Successfully copied file C:\Users\LX\AppData\Local\niemiro\Archive\ActionFiles\Cleanup.xml to C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml.
Successfully copied file C:\Users\LX\AppData\Local\niemiro\Archive\ActionFiles\Generalize.xml to C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml.
Successfully copied file C:\Users\LX\AppData\Local\niemiro\Archive\ActionFiles\Respecialize.xml to C:\Windows\System32\Sysprep\ActionFiles\Respecialize.xml.
Successfully copied file C:\Users\LX\AppData\Local\niemiro\Archive\ActionFiles\Specialize.xml to C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml.


Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Cleanup.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Cleanup.xml
Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Generalize.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Generalize.xml
Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Respecialize.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Respecialize.xml
Successfully restored ownership for C:\Windows\Sysnative\Sysprep\ActionFiles\Specialize.xml
Successfully restored permissions on C:\Windows\Sysnative\Sysprep\ActionFiles\Specialize.xml
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 4 datablocks.
Finish time: 2017-12-04 21:31:18.879
Script hash: XVK185eRLDGY10mKd0CJNM93MPTlDxurPXdxY5afuok=

----------------------EOF-----------------------[COLOR=#333333]
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

I am sorry to report these errors persist:
• 2017-11 Kumulatives Update für Windows 10 Version 1709 für amd64-basierte Systeme (KB4048955) – Fehler 0x800706ba
• 2017-11 Sicherheitsupdate für Adobe Flash Player für Windows 10 Version 1709 für x64-basierte Systeme (KB4048951) – Fehler 0x800706ba
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

  1. Stop Cryptographic Services (cryptsvc) by running "net stop cryptsvc" from Command Prompt as Admin.
  2. Delete or rename the C:\Windows\System32\catroot2 folder.
  3. Start cryptsvc by running "net start cryptsvc" from Command Prompt as Admin.
  4. C:\Windows\System32\catroot2 will be recreated. If it is not, restart the computer.
  5. Wait for all the catalog files from C:\Windows\System32\catroot to be imported into the catroot2 database. This may take up to an hour, so be patient.
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

sorry for the stretch of unresponsiveness, was busy. I will get back to you here as soon as I had the chance to action your most recent recommendation.
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

hmmm ... del C:\Windows\System32\catroot2 is refused, stating "Process can't access C:\Windows\System32\catroot2\edb.log since this is currently in use by another process" (in German). I have tried to stop cryptsvc before tho + cmd said it couldn't be stopped. entering net stop cryptsvc again, however, gets the msg "Cryptography services isn't started. Checking in TaskManager under Services cryptsvc is also listed as ended. :/
Stuck.
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Rename the catroot2 folder to catroot2.old and let me know if successful
 
Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

there was already one, but I made do:

C:\Windows\System32>net stop cryptsvc
Kryptografiedienste ist nicht gestartet.
Sie erhalten weitere Hilfe, wenn Sie NET HELPMSG 3521 eingeben.


C:\Windows\System32>del catroot2.old
Möchten Sie "C:\Windows\System32\catroot2.old\*" löschen (J/N)? j


C:\Windows\System32>dir catroot*


12.11.2017 20:50 <DIR> catroot
16.12.2017 19:15 <DIR> catroot2
17.12.2017 10:19 <DIR> Catroot2.bak
17.12.2017 10:20 <DIR> catroot2.old
0 Datei(en), 0 Bytes
4 Verzeichnis(se), 87.637.065.728 Bytes frei


C:\Windows\System32>ren catroot2.old catroot2.older


C:\Windows\System32>dir catroot*


12.11.2017 20:50 <DIR> catroot
16.12.2017 19:15 <DIR> catroot2
17.12.2017 10:19 <DIR> Catroot2.bak
17.12.2017 10:20 <DIR> catroot2.older
0 Datei(en), 0 Bytes
4 Verzeichnis(se), 87.636.910.080 Bytes frei


C:\Windows\System32>ren catroot2 catroot2.old


C:\Windows\System32>dir catroot*


Verzeichnis von C:\Windows\System32


12.11.2017 20:50 <DIR> catroot
17.12.2017 10:19 <DIR> Catroot2.bak
16.12.2017 19:15 <DIR> catroot2.old
17.12.2017 10:20 <DIR> catroot2.older
0 Datei(en), 0 Bytes
4 Verzeichnis(se), 87.637.041.152 Bytes frei
 
Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

how will I know when the recreation is complete? What I got so far is this:

Microsoft Windows [Version 10.0.16299.19]
(c) 2017 Microsoft Corporation. Alle Rechte vorbehalten.


C:\Users\LX>net start cryptsvc
Kryptografiedienste wird gestartet.
Kryptografiedienste wurde erfolgreich gestartet.




C:\Users\LX>cd C:\Windows\System32\catroot2


C:\Windows\System32\catroot2>dir
Datenträger in Laufwerk C: ist OS
Volumeseriennummer: D4EF-1B9E


Verzeichnis von C:\Windows\System32\catroot2


19.12.2017 07:30 <DIR> .
19.12.2017 07:30 <DIR> ..
19.12.2017 09:20 182.905 dberr.txt
19.12.2017 09:20 8.192 edb.chk
19.12.2017 09:20 2.097.152 edb.log
17.12.2017 20:53 2.097.152 edb00016.log
19.12.2017 07:22 2.097.152 edb00017.log
19.12.2017 07:30 2.097.152 edb00018.log
17.12.2017 18:53 2.097.152 edbres00001.jrs
17.12.2017 18:53 2.097.152 edbres00002.jrs
17.12.2017 20:02 2.097.152 edbtmp.log
17.12.2017 18:53 <DIR> {127D0A1D-4EF2-11D1-8608-00C04FC295EE}
17.12.2017 18:53 <DIR> {F750E6C3-38EE-11D1-85E5-00C04FC295EE}
9 Datei(en), 14.871.161 Bytes
4 Verzeichnis(se), 87.100.264.448 Bytes frei


C:\Windows\System32\catroot2>
 
Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

still no luck.
"• 2017-12 Kumulatives Update für Windows 10 Version 1709 für x64-basierte Systeme (KB4054517) – Fehler 0x800706be
• 2017-12 Sicherheitsupdate für Adobe Flash Player für Windows 10 Version 1709 für x64-basierte Systeme (KB4053577) – Fehler 0x800706ba
• Intel Corporation - Display - 10/16/2017 12:00:00 AM - 20.19.15.4835 – Fehler 0x800706be
• Update for Windows 10 Version 1709 for x64-based Systems (KB4058043) – Fehler 0x800706be"

View attachment cbs-2017-12-20-(09-40).zip
 
Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Right-click your C: drive and click Properties. Select Security Tab and take screenshot of that for me for each group or user name listed.
 
Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

pls find attached. The stupid box didn't allow for resize, so I had to scroll to a position showing the top and bottom line/s at least half :/
I hope it still conveys what you need to see; I think it is discernible, where there is a checkmark and where not.
View attachment Screens for SysNative.zip
 
Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

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 [CODE][/CODE] tags around the log to break up the text.


When done, go ahead and try updates.
 

Attachments

Re: [10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

didn't complete successfully:

>>SFCFix version 3.0.0.0 by niemiro.Start time: 2017-12-23 20:24:41.773
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\LX\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Sysnative\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat


Failed to backup file C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat with error code 0x570.


The file \\?\C:\Windows\Sysnative\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat is in use and must be replaced over a reboot.


Successfully pended file for replace over reboot: \\?\C:\Windows\Sysnative\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
Hash failure for file \\?\C:\Windows\Sysnative\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat.
Expected: SFDIddYuxYvxmB6LShdUFjwr72VlWhEiivSEdPPmIgs=
Found: Failed to generate hash - file may be in use.
PostRebootCorruptionDetection:: directive failed to complete successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\Windows\Sysnative\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat
Successfully restored permissions on C:\Windows\Sysnative\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\package_2987_for_kb4019472~31bf3856ad364e35~amd64~~10.0.1.6.cat
PostRebootRestorePermissions:: directive completed successfully.




Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2017-12-23 20:28:27.996
----------------------EOF-----------------------<<
 
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