Page 3 of 7 First 1234567 Last
  1. #41
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    The normal thing.


    • Ad Bot

      advertising
      Beep.

        
       

  2. #42

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

    also, "dir tmp*.cat" gets me 0 hits in that directory - there seem to be no files matching that search pattern. Standing by for further instructions. Do i just go ahead with the remaining steps?

  3. #43
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Yes, please.

  4. #44

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

    (ftr: cryptsvc did not need to be stopped as it wasn't running when i told it to stop, in case that matters. I did start it tho as instructed after renaming catroot2.)
    sadly, 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

    attached, pls find the latest set of logs : logs-2017-11-16-(23-16).zip

  5. #45
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Let's repeat this, but with verification.

    Please follow these instructions: https://social.technet.microsoft.com...integrity.aspx

    Ignore the Server2008 reference it works on W10.

  6. #46

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

    esentutl /p %systemroot%\System32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb finished stating "Repair completed. Database corruption has been repaired!"

    esentutl /g %systemroot%\System32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\catdb finished stating "Integrity check sucessful."

    I assumed you would like me to try normal Windows Update yet again after that and did so. Same result, sorry to say:
    • 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

    latest logs attached : logs-2017-11-16-(23-48).zip

  7. #47
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    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 One Drive or SendSpace and just provide the link.

  8. #48

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

    DISM concluded successfully; cbs.txt ended up really small, here you go : cbs.txt

  9. #49
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Run SFC again to see if it finds anything now.

  10. #50

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

    finished reporting corrupted files cbs-2017-11-17-(08-56).zip

    Is there maybe a repository somewhere from which we can obtain confirmedly intact versions of the afflicted files and replace them manually at the required position here? Would that make any sense? (Clutching for straws here.) Cheers for your continuedly patient support <3

  11. #51
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Yes, I'm sourcing all the replacement files from a clean copy from my virtual machine. I'll be with you shortly.

  12. #52
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Strange. Could you do SFC once more please. I can't see any corrupt files.

  13. #53

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

    sure. pls find attached cbs-2017-11-18-(11-04).zip

  14. #54
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Install Update with DISM


    1. Download the update MSU here:
      http://download.windowsupdate.com/d/...a7b1379c1f.msu
    2. Copy the MSU file to a convenient location (such as C:\temp).
    3. Click on the Start button and in the search box, type Command Prompt
    4. When you see Command Prompt on the list, right-click on it and select Run as administrator
    5. When command prompt opens, copy and paste the following commands into it, press enter after each

      cd C:\temp

      replace C:\temp with your path if different

      expand {update name}.msu -f:* C:\temp

      replace {update name} with the name of the MSU file downloaded in step 1

      DISM.exe /Online /Add-Package /PackagePath:C:\temp\{update name}.cab
    6. You should receive the message:
      The operation completed successfully.
      Restart Windows to complete this operation.
      Do you want to restart the computer now (Y/N)?
    7. Make sure to allow the computer to restart if prompted.

      If you receive any other message:
    8. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
    9. Paste (Ctrl+V) it into your next post.
    10. Zip and attach C:\Windows\Logs\CBS\CBS.log

  15. #55

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

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

    C:\>cd _install

    C:\_install>expand windows10.0-kb4048951-x64_35f2f534365f41e09b9d707b220b1ea7b1379c1f.msu -f:* C:\_install
    Microsoft (R) Dateiexpansions-Hilfsprogramm
    Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

    C:\_install\WSUSSCAN.cab wird zur Extrahierungswarteschlange hinzugefügt
    C:\_install\Windows10.0-KB4048951-x64.cab wird zur Extrahierungswarteschlange hinzugefügt
    C:\_install\Windows10.0-KB4048951-x64-pkgProperties.txt wird zur Extrahierungswarteschlange hinzugefügt
    C:\_install\Windows10.0-KB4048951-x64.xml wird zur Extrahierungswarteschlange hinzugefügt

    Dateien werden erweitert ....

    Erweitern der Dateien ist abgeschlossen ...
    4 Dateien insgesamt

    C:\_install>DISM.exe /Online /Add-Package /PackagePath:C:\_install\windows10.0-kb4048951-x64_35f2f534365f41e09b9d707b220b1ea7b1379c1f.cab

    Tool zur Imageverwaltung für die Bereitstellung
    Version: 10.0.16299.15

    Abbildversion: 10.0.16299.19

    Fehler beim Öffnen - C:\_install\windows10.0-kb4048951-x64_35f2f534365f41e09b9d707b220b1ea7b1379c1f.cab Fehler: 0x80070003
    Fehler beim Öffnen - C:\_install\windows10.0-kb4048951-x64_35f2f534365f41e09b9d707b220b1ea7b1379c1f.cab Fehler: 0x80070003
    Fehler: 3
    Fehler beim Öffnen - C:\_install\windows10.0-kb4048951-x64_35f2f534365f41e09b9d707b220b1ea7b1379c1f.cab Fehler: 0x80070003

    Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".


    [noticed the .cab was named differently from the dowload package, retried with name found on cab in dir]


    C:\_install>DISM.exe /Online /Add-Package /PackagePath:C:\_install\Windows10.0-KB4048951-x64.cab


    Tool zur Imageverwaltung für die Bereitstellung
    Version: 10.0.16299.15

    Abbildversion: 10.0.16299.19

    1 von 1 werden verarbeitet - Paket "Package_for_KB4048951~31bf3856ad364e35~amd64~~10.0.1.0" wird hinzugefügt
    [==========================100.0%==========================]
    Fehler - Package_for_KB4048951: 0x800706be

    Fehler: 1726

    Der Remoteprozeduraufruf ist fehlgeschlagen.

    Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log".

    C:\_install>

    [end of copy]

    + here's the logs:

    logs-2017-11-18-(17-33).zip

  16. #56
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Click Start and enter Event Viewer.

    Right-click the appropriate log file (Application, Security, System, Directory Service, or File Replication Service). I need System and Application logs.

    Click Save Log File As.

    Type a name for the file, and click Save.

    Zip the files up and attach them for me to review.

  17. #57

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


  18. #58
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    Do you use: Intel Rapid Storage Technology?

  19. #59

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

    not that I was aware of it. Probably one of those thingies that you only notice once you shut them off. Want me to try anything with/out that?
    Cheers - A / EMS

  20. #60
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    7,484
    • specs System Specs
      • Motherboard:
        ASUS MAXIMUS ROG HERO X
      • CPU:
        Intel Core i7-8700K 3.7GHz
      • Memory:
        Crucial 2x8GB DDR4 2666 MHz
      • Graphics:
        Gigabyte GTX 1080 G1 Gaming 8 GB
      • Sound Card:
        Asus Xonar DSX
      • Hard Drives:
        WD Caviar Black 1TB SATA III 7200rpm, WD Caviar Black 6TB SATA III 7200rpm
      • Disk Drives:
        Samsung 960 Evo 256GB NVME PCIe
      • Power Supply:
        Corsair HX 750W 80+ Platinum
      • Case:
        Fractal Design Define R6
      • Cooling:
        Noctua NH-D14
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1709 x64

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

    I want you to update it if you have it.

Page 3 of 7 First 1234567 Last

Similar Threads

  1. Replies: 7
    Last Post: 01-17-2018, 03:56 PM
  2. Replies: 58
    Last Post: 07-21-2015, 06:47 PM
  3. Replies: 12
    Last Post: 01-31-2014, 03:36 PM
  4. [SOLVED] Windows Update stopped working (Manual updates not working either)
    By AndreB in forum Windows Update
    Replies: 15
    Last Post: 07-05-2013, 07:00 AM

Log in

Log in