Page 1 of 7 12345 ... Last
  1. #1

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

    Hello; I hope I haven't missed anything relevant, looking thru the forum before posting this issue, as it is a variation of the trouble with (I guess) fdeploy.dll, fde.dll, gpedit.dll, gptext.dll covered in several threads already here and elsewhere. Most occurences got solved by repair installs (on older systems); more tenacious instances by per individualized applications of SFCFix, the beacon which drew me to this place. Sadly, I haven't been able to get SFCFix to do an analysis on my end; otherwise I would have already included the information provided by that.

    Situation

    After having messed up my system (details further below), I seem to have managed to get most of it back to working nominally per installation of the latest upgrade available from Access Denied - so far, so nice.

    • DISM /Online /Cleanup-Image /Restore Health finished successfully after that according to prompt.
      However:
    • sfc /scannow still complains about corrupted files (which was part of what caused me to go thru the upgrade in the first place).
    • The corrupted files are the 4 listed above, according to cbs.log.

    Observable effects (at least the ones I am currently aware of:)



    • Windows diagnostic services are inoperable, coming back with the famous (German version of) "The problem cannot be diagnosed due to a problem" (potentially not translated verbatim here; my system runs in German). As far as I could ascertain so far, this affects all problem-solving subtools coming with Windows (under System/Settings > TroubleShooting or whatever it's called on English versions; you'll probably know which one/s I mean).


    Where I'm stuck now



    • Looking for help I found your forum and SFCFix and tried running it for analysis. But I must be doing something wrong, since I only get this as result:

      SFCFix version 3.0.0.0 by niemiro.
      Start time: 2017-09-28 11:35:11.553
      Microsoft Windows 10 Build 15063 - amd64
      Not using a script file.


      AutoAnalysis::
      WARNING: Failed to check store directories with return code 1 and error code ERROR_FILE_NOT_FOUND. COMPONENTS hive may be corrupt.


      WARNING: Components hive failed load test and may be corrupt.


      WARNING: Components hive failed final reload test with error code ERROR_PRIVILEGE_NOT_HELD and may be corrupt.


      SUMMARY: No corruptions were detected.
      AutoAnalysis:: directive completed successfully.


      Successfully processed all directives.
      SFCFix version 3.0.0.0 by niemiro has completed.
      Currently storing 0 datablocks.
      Finish time: 2017-09-28 11:35:41.947
      ----------------------EOF-----------------------

      I have tried launching it from various locations (c:\ as well as C:\Windows\Logs\CBS), from an elevated cmd prompt as well as thru a "Run As Administrator" pointer; all to no avail. The CBS.log does exist tho, and I can provide it, if this should shed relevant light.


      How should I be running this to get meaningful results to share here?


      Thank you very much for your help in advance + kind regards;
      LX


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    Hi and welcome to Sysnative! Sorry about the delay. Are you still in need of assistance?

  3. #3

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

    Hello + sadly, yes. Thank you for getting back to me. I'd appreciate what help I can get. Cheers.

  4. #4
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    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.

  5. #5

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

    Hello, pls find attached, hth.

    cbs.txt.zip

  6. #6
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    Retrieve Components Hive
    1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
    2. Please copy this file to your desktop.
    Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
    3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
    4. The file will likely be too large to upload here so please upload toa file sharing service and just provide the link here.

  7. #7

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

    hello; here you go; hope this serves :

    COMPONENTS.zip - Google Drive

  8. #8
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    What happens if you check for updates and try to install them?
    Also, what updates are offered?

  9. #9

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

    it appears this stopped working some time ago. :/ I'm seing a message informing me, that "there were problems but that Windows will keep trying"; the updates currently listed as queued are


    • 2017-06 Update für Windows 10 Version 1703 für x64-basierte Systeme (KB4022405) – Fehler 0x800706be
    • 2017-10 Kumulatives Update für Windows 10 Version 1703 für x64-basierte Systeme (KB4041676) – Fehler 0x800706ba
    • 2017-10 Sicherheitsupdate für Adobe Flash Player für Windows 10 Version 1703 für x64-basierte Systeme (KB4049179) – Fehler 0x800706ba


    (where "Fehler" is German for "error" :/ ) I'm assuming the KB-codes will nonetheless inform you which update packages are concerned, right? Cheers -
    Last edited by LXM; 11-11-2017 at 03:31 PM. Reason: (misspelling/s)

  10. #10
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    Download the October Quality Rollup from this link, and try installing it. If it fails, please provide CBS.log

  11. #11

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

    Hello, the MSU stopped after conducting a search for updates on my computer, giving the message: "The update is not apt for your computer".

    As per your request, I ran SFC again after this attempt. Please find the latest version of CBS log attached. cbs-2017-11-12-(10-29).zip

  12. #12
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    Are you willing to try upgrading to the latest W10 build?

    Please boot your computer into a Clean Boot state and do the following:

    1. Download the Media Creation Tool to your desktop. Go ahead and run this. Note: Click the Download tool now button when you are at this link.
    2. Accept the license agreement
    3. Keep the default which is to Upgrade your PC and click Next.
    4. Go ahead and run this through and let me know when complete.

    Doing it this way will keep all your data and programs intact. As always though, make sure you have a backup of any critical data in case something unexpected happens.

    Let me know how it goes.

  13. #13

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

    Hello; i had done this before I came posting here; see initial post in which it a.o. says >>I seem to have managed to get most of it back to working nominally per installation of the latest upgrade available from Access Denied<< which .did. mitigate much of my plight, just not its entirety. That was around Sept 28th, tho. Has there been a newer release since? Do you think repeating will improve further?

  14. #14
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    A new windows 10 build has been released in the meantime. I think it's worth a shot.

  15. #15

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

    OK, *sigh* - I'll give it a go and let you know how it went. If you hear not back from me, we have imploded, my machine and I :-P Cheers!

  16. #16

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

    OK, did that and survived :) Apparently a little somethign changed: When I check for Windows Updates now, only 2 remain failing:


    • 2017-10 Sicherheitsupdate für Adobe Flash Player für Windows 10 Version 1709 für x64-basierte Systeme (KB4049179) – Fehler 0x800706be (this one was failing earlier, too, see above)
    • Update für Adobe Flash Player unter Windows 10 Version 1709 für x64-basierte Systeme (KB4051613) – Fehler 0x800706ba (that's a new one)


    The original observable effect >>Windows diagnostic services are inoperable, coming back with the famous (German version of) "The problem cannot be diagnosed due to a problem" (potentially not translated verbatim here; my system runs in German). As far as I could ascertain so far, this affects all problem-solving subtools coming with Windows (under System/Settings > TroubleShooting or whatever it's called on English versions; you'll probably know which one/s I mean).<<

    persists.

  17. #17
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    Please run SFC and attach CBS.log.

  18. #18

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

    cbs 2017-11-13-(22-40).zip here you go. Pls excuse delayed response/s during workweek. Cheers.

  19. #19
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    23
    Posts
    12,169
    • 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 1803 x64

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

    Great, SFC is clean. Attempt the updates again, and when they fail attach CBS.log (Do not run SFC before sttaching!) Just try them, and attach if/when they fail!

  20. #20

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

    the two remaining updates are still failing. Here is the latest cbs log : cbs-2017-11-14-(08-40).rar - Cheers

Page 1 of 7 12345 ... 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