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

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

I can't seem to find any sign of it being installed. Where would it reside if it was present on my system?
 
Re: [W10Stdv1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

If it was present, you'd see it in the Taskbar.

Try the following, open CMD as admin and enter:

Code: 
net start cryptsvc

Hit Enter and let me know what the result is. If the service starts successfully, go ahead and check for updates.
 
Re: [W10Stdv1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

If it was present, you'd see it in the Taskbar.

apparently not present.

Try the following, open CMD as admin and enter: Code: net start cryptsvc Hit Enter and let me know what the result is. If the service starts successfully,

yes it did.

go ahead and check for updates.

Did. Still no luck.
• 2017-11 Kumulatives Update für Windows 10 Version 1709 für amd64-basierte Systeme (KB4048955) – Fehler 0x800706be
• 2017-11 Sicherheitsupdate für Adobe Flash Player für Windows 10 Version 1709 für x64-basierte Systeme (KB4048951) – Fehler 0x800706ba

Sorry. + regards
 
Re: [W10Stdv1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Okay, let's try reseting WU Components:

Download the following file.
Create a new folder on your Desktop.
Extract it to a new folder on your Desktop you've created in the previous step.
Right-click ResetWUEng.cmd file and select Run as Administrator.
A windows will appear prompting you if you want to continue with the process. Please press Y.
Another menu will appear. Press 2: Reset Windows Update Components.
Verify that you have selected number 2 and hit Enter.
Wait until the process is complete.
You should see the message: The operation completed successfully.
Press any key to continue. . .

Close the window and reboot.

Try updating once again. If it fails, please attach CBS.log
 
Re: [W10Stdv1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

once the windows update window opened it said all was current. i told it to check for updates and it found our 2 usual suspects. Trying to install them i got the usual errors:
• 2017-11 Kumulatives Update für Windows 10 Version 1709 für amd64-basierte Systeme (KB4048955) – Fehler 0x800706be
• 2017-11 Sicherheitsupdate für Adobe Flash Player für Windows 10 Version 1709 für x64-basierte Systeme (KB4048951) – Fehler 0x800706be

here's the most recent log: View attachment cbs-2017-11-21-(20-45).zip
 
Re: [W10Stdv1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

It appears that your hard drive may be failing, we can try to repair the current issues, but please bear in mind that your HDD may fail very soon and it may continue to work for years to come. There's no way of knowing for sure. if you haven't yet, make sure you BACKUP ALL IMPORTANT DATA RIGHT AWAY! Once that's done, proceed with instructions below:


chkdsk /r

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. 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

    chkdsk /r
  4. Reboot
  5. Download ListChkdskResult.exe (by SleepyDude) from the link below:

    https://dl.dropboxusercontent.com/u/...kdskResult.exe
  6. Double click on it to run it. It will take a few seconds to scan, then it will open a Notepad window with the log. Copy and paste the contents of this into your next post please!
 
Re: [W10Stdv1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Hu, comes back in german. Still useful to you?:
[BEGIN COPY]
ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013


------< Log generate on 22.11.2017 20:40:37 >------
Category: 0
Computer Name: unknown
Event Code: 1001
Record Number: 66296
Source Name: Microsoft-Windows-Wininit
Time Written: 11-22-2017 @ 09:22:52
Event Type: Informationen
User:
Message:


Dateisystem auf C: wird überprüft.
Der Typ des Dateisystems ist NTFS.
Die Volumebezeichnung lautet OS.


Eine Datenträgerüberprüfung ist geplant.
Die Datenträgerüberprüfung wird jetzt ausgeführt.


Phase 1: Die Basisdatei-Systemstruktur wird untersucht...
530944 Datensätze verarbeitet.


Dateiüberprüfung beendet.
18953 große Datensätze verarbeitet.


0 ungültige Datensätze verarbeitet.




Phase 2: Die Dateinamenverknüpfung wird untersucht...
Das Kennzeichen für geringe Datendichte im Attribut für Standardinformationen in der Datei "0x17d8d"
sollte nicht festgelegt werden.
Die geringe Datendichte im Datensatzsegment 97677 wird korrigiert.
49632 Analysedatensätze verarbeitet.


674240 Indexeinträge verarbeitet.


Indexüberprüfung beendet.
0 nicht indizierte Dateien überprüft.


0 nicht indizierte Dateien wiederhergestellt.


49632 Analysedatensätze verarbeitet.




Phase 3: Sicherheitsbeschreibungen werden untersucht...
7279 nicht verwendete Indexeinträge aus Index $SII der Datei 0x9 werden aufgeräumt.
7279 nicht verwendete Indexeinträge aus Index $SDH der Datei 0x9 werden aufgeräumt.
7279 nicht verwendete Sicherheitsbeschreibungen werden aufgeräumt.
CHKDSK komprimiert den Datenstrom für die Sicherheitsbeschreibung
Überprüfung der Sicherheitsbeschreibungen beendet.
71649 Datendateien verarbeitet.


CHKDSK überprüft USN-Journal...
37328424 USN-Bytes verarbeitet.


Die Überprüfung von USN-Journal ist abgeschlossen.


Phase 4: Es wird nach fehlerhaften Clustern in Benutzerdateidaten gesucht...
530928 Dateien wurden verarbeitet.


Dateidatenüberprüfung beendet.


Phase 5: Es wird nach fehlerhaften, freien Clustern gesucht...
19559809 freie Cluster verarbeitet.


Verifizierung freien Speicherplatzes ist beendet.
Fehler in Volumebitmap werden berichtigt.


Es wurden Korrekturen am Dateisystem vorgenommen.
Es sind keine weiteren Aktionen erforderlich.


390703103 KB Speicherplatz auf dem Datenträger insgesamt
311582404 KB in 325788 Dateien
225368 KB in 71652 Indizes
0 KB in fehlerhaften Sektoren
656091 KB vom System benutzt
65536 KB von der Protokolldatei belegt
78239240 KB auf dem Datenträger verfügbar


4096 Bytes in jeder Zuordnungseinheit
97675775 Zuordnungseinheiten auf dem Datenträger insgesamt
19559810 Zuordnungseinheiten auf dem Datenträger verfügbar


Interne Informationen:
00 1a 08 00 f6 0f 06 00 98 88 0b 00 00 00 00 00 ................
48 08 00 00 98 b9 00 00 00 00 00 00 00 00 00 00 H...............


Die Überprüfung des Datenträgers wurde abgeschlossen.
Bitte warten Sie bis der Computer neu gestartet wurde.


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

failed again, same 2 packages.
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

JcJ91sx.png
GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:



  • Download GSmartControl and save it on your Desktop;
  • Execute gsmartcontrol.exe; Let the install complete and launch the programme.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
    info_failing.png
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

"Test #","Type","Status","% Completed","Lifetime hours","LBA of the first error"1,"Extended offline","Completed without error","100%","8056","-"

no attributes red or pink
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

+ perchance I stumbled across another symptom which may or may not be significant: The "Windows Defender Security Center" fails to start and cannot be launched manually either; it will switch to looking active for a few seconds, 10-20 maybe, and then reverts to stating "The threat service was terminated. Please restart it now." When I click the 1 available button "Restart now" it'll display a box stating "Unexpected error. Unfortunately there was a problem. Try again." Button: "Close".
:/
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

I know about that.
Run CMD as admin and enter the following command:

sc start WinDefend Enable


Hit Enter and let me know the result,
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

SERVICE_NAME: WinDefend
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x1
WAIT_HINT : 0x7530
PID : 12568
FLAGS :
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and update your system just like you have in the past.
3. Stop Process Monitor as soon the update fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 attach the LogFile.PML file as well as your CBS.log.
​
 
Re: [W10v1703b15063 x64] Diagnostic tools stopped working. Updating didn't help.

Please zip and attach the following file: C:\Windows\System32\catroot2\dberr.txt

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

Attachments

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