Getting Windows Update Error "0x800706d9"

Discussion in 'Windows 10' started by slackeritguy, Nov 24, 2015.

  1. slackeritguy

    slackeritguy MDL Member

    Jun 27, 2013
    163
    25
    10
    #1 slackeritguy, Nov 24, 2015
    Last edited by a moderator: Apr 20, 2017
    So, I just updated my main PC to Windows 10 Pro 10586/TH2 (clean install), everything went super smooth with the installation.

    Now, before going online, I made sure I ran the following apps to remove all of the Telemetry services, tasks, etc.

    These were the apps I ran:

    - Toggle Tweaker 2.9 (latest)
    - Spybot Anti-Beacon 1.5 (latest)
    - DWS from WZor.net 1.6 (latest)

    Now, after all of that, I tried to update Windows through Windows Update and I got this error code:

    Code:
    0x800706d9
    What's preventing my PC from downloading updates through Windows Update?

    Thanks.
     
  2. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,204
    978
    90
    #2 LiteOS, Nov 24, 2015
    i google it
    maybe firewall ?
     
  3. slackeritguy

    slackeritguy MDL Member

    Jun 27, 2013
    163
    25
    10
    #3 slackeritguy, Nov 24, 2015 (OP)
    Firewall's disabled through Services.msc.
     
  4. lobo11

    lobo11 TOMAHAWK CHOP

    Feb 16, 2012
    6,584
    5,362
    210
    #4 lobo11, Nov 24, 2015
    Last edited by a moderator: Apr 20, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. LiteOS

    LiteOS Windowizer

    Mar 7, 2014
    2,204
    978
    90
    #5 LiteOS, Nov 24, 2015
    check in gpedit.msc if there something relate to updates is set
     
  6. slackeritguy

    slackeritguy MDL Member

    Jun 27, 2013
    163
    25
    10
    #6 slackeritguy, Nov 24, 2015 (OP)
    That actually worked, thanks Lobo.

    Bummer that I have to enable Firewall's service for this to work, is there a way to absolutely disable Windows Firewall without actually disabling its service?
     
  7. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,256
    94,680
    450
    #7 Enthousiast, Nov 24, 2015
    This is caused by one of the non ms/third party software/tweakcmd's you ran ;)