Page 2 of 7 First 123456 ... Last
  1. #21
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    Download the attached file.
    Right click on it and select Run as Administrator.
    A CMD windows will appear.
    Wait for it to finish.
    Try Windows Update and attach CBS.log if any fail.

    Note: It will take longer and that is perfectly normal.
    Attached Files Attached Files


    • Ad Bot

      advertising
      Beep.

        
       

  2. #22

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

    did that. Update still doesn't complete fully; however, apparently it is now 2 other packages that don't finish:

    • 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

    attached pls find latest cbs : cbs-2017-11-15-(00-30).zip - Cheers

  3. #23
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    Farbar Service Scanner
    1. Download Farbar Service Scanner from here, and move it to the Desktop
    2. Right-click on FSS.exe > Run as Administrator
    3.
    Checkmark everything, and click Scan
    4. Once it finishes, Notepad will open FSS.txt on your Desktop. Copy and paste everything in it in your next reply

  4. #24

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

    Farbar Service Scanner Version: 27-01-2016
    Ran by LX (administrator) on 15-11-2017 at 21:02:10
    Running from "C:\Users\LX\Desktop"
    Microsoft Windows 10 Home (X64)
    Boot Mode: Normal
    ****************************************************************


    Internet Services:
    ============


    Connection Status:
    ==============
    Localhost is accessible.
    LAN connected.
    Google IP is accessible.
    Google.com is accessible.
    Yahoo.com is accessible.




    Windows Firewall:
    =============


    Firewall Disabled Policy:
    ==================




    System Restore:
    ============


    System Restore Policy:
    ========================




    Security Center:
    ============




    Windows Update:
    ============


    Windows Autoupdate Disabled Policy:
    ============================




    Windows Defender:
    ==============
    WinDefend Service is not running. Checking service configuration:
    The start type of WinDefend service is set to Demand. The default start type is Auto.
    The ImagePath of WinDefend service is OK.




    Windows Defender Disabled Policy:
    ==========================
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Defender]
    "DisableAntiSpyware"=DWORD:1




    Other Services:
    ==============




    File Check:
    ========
    C:\Windows\System32\nsisvc.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0030720 ____A (Microsoft Corporation) 3BA4E9585E9D7D7E6E68A18184DDDBF2


    C:\Windows\System32\drivers\nsiproxy.sys
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0044544 ____A (Microsoft Corporation) 958921BB7AE2671983743FDA0DD587C4


    C:\Windows\System32\drivers\afd.sys => File is digitally signed
    C:\Windows\System32\drivers\tdx.sys => File is digitally signed
    C:\Windows\System32\Drivers\tcpip.sys => File is digitally signed
    C:\Windows\System32\dnsrslvr.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0286720 ____A (Microsoft Corporation) 4ACA3CE75B4C2243299C24A715E9B3CE


    C:\Windows\System32\dnsapi.dll => File is digitally signed
    C:\Windows\SysWOW64\dnsapi.dll => File is digitally signed
    C:\Windows\System32\mpssvc.dll
    [2017-11-12 20:16] - [2017-11-12 20:16] - 0925184 ____A (Microsoft Corporation) A2C216233E8A1CF98315E76EBF69D73D


    C:\Windows\System32\bfe.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0841216 ____A (Microsoft Corporation) 86CAB4060251D418B6449D6CBCC852A6


    C:\Windows\System32\drivers\mpsdrv.sys
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0075776 ____A (Microsoft Corporation) F36E4074C66DD31855A8D79EF0AE8066


    C:\Windows\System32\SDRSVC.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0145408 ____A (Microsoft Corporation) 368180051766E4289E3D47AF21F2668C


    C:\Windows\System32\vssvc.exe
    [2017-09-29 14:42] - [2017-09-29 14:42] - 1558016 ____A (Microsoft Corporation) 16144D396BFFEFDB0B8A2C964CBAD35D


    C:\Windows\System32\wscsvc.dll
    [2017-09-29 14:42] - [2017-09-29 14:42] - 0246784 ____A (Microsoft Corporation) 39DA352FAD220E83CE64DE8DCCB9736B


    C:\Windows\System32\wbem\WMIsvc.dll
    [2017-09-29 14:42] - [2017-09-29 14:42] - 0220160 ____A (Microsoft Corporation) 0FBD5D358094E254A1508832D4042FF7


    C:\Windows\System32\wuaueng.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 2782720 ____A (Microsoft Corporation) D7CE60FDA88A6743D96359ED91BEEE00


    C:\Windows\System32\qmgr.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 1345536 ____A (Microsoft Corporation) E223918B4E0B28CF7BE132C30D1E161A


    C:\Windows\System32\es.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0450560 ____A (Microsoft Corporation) 6A5FA501A2D96001391FF3CBA32935AB


    C:\Windows\System32\cryptsvc.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0094720 ____A (Microsoft Corporation) D64EF74FC6DA47EC2E460076F299E77D


    C:\Program Files\Windows Defender\MpSvc.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 2306456 ____A (Microsoft Corporation) 201C15629DD72D071CF885DEA3203328


    C:\Windows\System32\ipnathlp.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0600576 ____A (Microsoft Corporation) B08841DD1EF979C5C6F9A7F101BA3D9C


    C:\Windows\System32\iphlpsvc.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0820224 ____A (Microsoft Corporation) 0076CE11539416052A7A79B2DCC53E6D


    C:\Windows\System32\svchost.exe
    [2017-09-29 14:41] - [2017-09-29 14:41] - 0048688 ____A (Microsoft Corporation) 440684C4F823AAE2CC587363F9C477A6


    C:\Windows\System32\rpcss.dll
    [2017-09-29 14:41] - [2017-09-29 14:41] - 1117184 ____A (Microsoft Corporation) 79BDBB684629A526CCD958F06B9D6FAD






    **** End of log ****

    this? :) Cheers!

  5. #25
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    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...
    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.
    6. Double-click on Repair_Windows.exe to open.
    7. The program should open.
    8. 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. Please click the Unselect All button and then click to enable only the following ones:


    14 - Remove Temp Files
    17 - Repair Windows Updates


    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.

    12. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.



  6. #26

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

    Did as told, thanks.
    Assuming you'd want to know whether updates work/ed afterwards, I checked, getting the response "Wir konnten keine Verbindung mit dem Updatedienst herstellen. Wir versuchen es später erneut. Alternativ können Sie es jetzt versuchen. Überprüfen Sie Ihre Internetverbindung, falls es immer noch nicht funktioniert." which translates to "We could not establish a connection with the update service. We will try again later. Alternatively you can attempt now. Please check your internet connection if it still isn't working." I tried again and my internet is up. No luck. I'm doubtful if another reboot will change much, as this was attempted after the machine restarted after the above repair run.
    Do you want the latest cbs? If yes: before or after an(other) sfc?
    Cheers.

  7. #27
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    I need some additional info:

    1. Do you use any kind of VPN/networking software?
    2. Is Windows Update service started? Check in services.msc Also check the Dependencies by double clciking the Windows Update service. You should see Remote Procedure Call. Check that it's running and is set to Automatic startup type.
    3. Do you use a static IP address?
    4. Do you use proxies?
    5. What antivirus software/firewall are you using?

    Also, please do the following:

    Step#1 - FRST Fix
    NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
    1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
    Note: You need to run the 64-bit Version so please ensure you download that one.
    2. Download attached file and save it to the Desktop.
    Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
    3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
    4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
    5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

    Before posting the results, please go ahead and run Windows Updates. If the issue is still there, along Fixlog, please post your WindowsUpdate.log:

    C:\Windows\WindowsUpdate.log
    Attached Files Attached Files

  8. #28

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

    hu; when I got back to the machine to act on your most recent reply, Windows Update managed to connect. Result is these two failing to install again:
    • 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

    Nonetheless, here's the information you requested:

    1. Do you use any kind of VPN/networking software?
    I have TorGuard installed but it was neither engaged nor running disengaged during any of the steps discussed so far.

    2. Is Windows Update service started? Check in services.msc
    At this very moment it appears to be not, but it is set to automatic start type (start by trigger)

    Also check the Dependencies by double clciking the Windows Update service. You should see Remote Procedure Call.
    Yes that's there.

    Check that it's running and is set to Automatic startup type.

    It does now.

    3. Do you use a static IP address?
    not that I know
    4. Do you use proxies?
    unless torguard is running and engaged I don't

    5. What antivirus software/firewall are you using?
    AVG Internet Security 17.8.3036

    After reviewing that, do you want me to proceed with FRS64 + fixlist.txt run?

    Cheers.

  9. #29
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    Yes, I do.

  10. #30

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

    Hmmmm, I see no "fix" button. The programm launched in German and shows 4 buttons, saying (left to right) : Examine ("Untersuchen"), File Search ("Datei-Suche"), Registry Search ("Regiytry-Suche"), Remove ("Entfernen"). Did I do something wrong?

  11. #31
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    No, press Entfernen.

  12. #32

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

    Errors persist:
    • 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

    Here's the content of fixlog.txt :

    Entferungsergebnis von Farbar Recovery Scan Tool (x64) Version: 15-11-2017
    durchgeführt von LX (16-11-2017 01:38:29) Run:1
    Gestartet von C:\Users\LX\Desktop
    Geladene Profile: LX (Verfügbare Profile: LX)
    Start-Modus: Normal
    ==============================================


    fixlist Inhalt:
    *****************
    cmd: sc config trustedinstaller start=auto
    cmd: net start trustedinstaller
    cmd: fsutil resource setautoreset true %SystemDrive%\
    cmd: attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
    cmd: echo y | del %SystemRoot%\System32\Config\TxR\*
    cmd: attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
    cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.tm*
    cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.blf
    cmd: echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms
    EmptyTemp:
    *****************




    ========= sc config trustedinstaller start=auto =========


    [SC] ChangeServiceConfig ERFOLG


    ========= Ende von CMD: =========




    ========= net start trustedinstaller =========


    Windows Modules Installer wird gestartet.
    Windows Modules Installer wurde erfolgreich gestartet.




    ========= Ende von CMD: =========




    ========= fsutil resource setautoreset true %SystemDrive%\ =========


    Der Vorgang wurde abgeschlossen.


    ========= Ende von CMD: =========




    ========= attrib -r -s -h %SystemRoot%\System32\Config\TxR\* =========




    ========= Ende von CMD: =========




    ========= echo y | del %SystemRoot%\System32\Config\TxR\* =========


    M”chten Sie "C:\WINDOWS\System32\Config\TxR\*" l”schen (J/N)? y
    M”chten Sie "C:\WINDOWS\System32\Config\TxR\*" l”schen (J/N)?


    ========= Ende von CMD: =========




    ========= attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* =========




    ========= Ende von CMD: =========




    ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.tm* =========


    C:\WINDOWS\System32\SMI\Store\Machine\*.tm* konnte nicht gefunden werden


    ========= Ende von CMD: =========




    ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.blf =========


    C:\WINDOWS\System32\SMI\Store\Machine\*.blf konnte nicht gefunden werden


    ========= Ende von CMD: =========




    ========= echo y | del %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms =========


    C:\WINDOWS\System32\SMI\Store\Machine\*.regtrans-ms konnte nicht gefunden werden


    ========= Ende von CMD: =========




    =========== EmptyTemp: ==========


    BITS transfer queue => 6053888 B
    DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 17266089 B
    Java, Flash, Steam htmlcache => 708970149 B
    Windows/system/drivers => 661380 B
    Edge => 4330146 B
    Chrome => 398259316 B
    Firefox => 3498193 B
    Opera => 1693108 B


    Temp, IE cache, history, cookies, recent:
    Default => 6656 B
    Users => 0 B
    ProgramData => 0 B
    Public => 0 B
    systemprofile => 0 B
    systemprofile32 => 0 B
    LocalService => 10852 B
    NetworkService => 598662128 B
    LX => 2579805 B


    RecycleBin => 36135444 B
    EmptyTemp: => 1.7 GB temporäre Dateien entfernt.


    ================================




    Das System musste neu gestartet werden.


    ==== Ende von Fixlog 01:43:39 ====

    + here's the content of C:\Windows\WindowsUpdate.log :


    Windows Update logs are now generated using ETW (Event Tracing for Windows).
    Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log.


    For more information, please visit https://go.microsoft.com/fwlink/?LinkId=518345


    -----------------------
    which is probably not useful. :/ I went to check this document, but couldn't make much sense of it; the only promising link in it went 404.

    Sorry. Can you pilot me thru getting you that update log?

  13. #33
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    Ah, yes, I forgot about the change. Sorry.
    Please attach CBS.log and WindowsUpdate.log

    To get WindowsUpdate.log, please run Powershell as administrator and enter the following command:

    Get-WindowsUpdateLog



    Hit Enter, a file called WindowsUpdate.log will likely appear on your Desktop.

    Please zip it up and attach.

    Thanks.

  14. #34

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

    zipped and attached.

    WU-andCBS-logs-2017-11-16-(09-40).zip

    :) Cheers

  15. #35
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    Could you please completely remove AVG Internet Security from your system using its removal utility just for troubleshooting purposes?

    Afterwards, try updates again.

  16. #36

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

    completely removed avg internet security, re-attempted updates. errors persist:
    • 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 fnd the latest tound of logs : logs-2017-11-16-(19-34).zip

  17. #37
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    Download this file: http://download.windowsupdate.com/d/...8ca16bf632.msu

    Reboot your computer into a Clean Boot state: https://support.microsoft.com/en-ca/...oot-in-windows

    Attemp to run the update from the .msu file you've downloaded.

  18. #38

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

    sadly, this too failed. attached find the latest round of logs : logs-2017-11-16-(22-02).zip

  19. #39
    Moderator
    BSOD Kernel Dump Analyst
    Windows Update Senior Analyst
    softwaremaniac's Avatar
    Join Date
    Oct 2014
    Location
    Croatia
    Age
    22
    Posts
    5,201
    • specs System Specs
      • Motherboard:
        ASRock Fatal1ty P67 Main Board
      • CPU:
        Intel Core i7-2700K 3.5GHz
      • Memory:
        Crucial 2x8GB DDR3 1600 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 840 Evo 250GB
      • Power Supply:
        Corsair GS 700W
      • Case:
        Silverstone KL04B Case
      • Cooling:
        CoolerMaster Arctic Freezer 7 Pro
      • Display:
        Philips Brilliance BDM4065UC 4K 3840x2160
      • Operating System:
        Windows 10 Pro 1703 x64

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

    1. Remove any tmp*.cat files in the
    "%systemroot%\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}" folder.

    2. Run Command Prompt as admin and enter the following:

    net stop cryptsvc

    rename %systemroot%\System32\Catroot2 oldcatroot2

    net start cryptsvc


    Press Enter after each of the commands.

    Try Windows Update again.

  20. #40

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

    double-check: run regular windows update again (the normal thing, via systems settings) or retry that .msu i downloaded per you previous instruction? cheers

Page 2 of 7 First 123456 ... 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