Skip to content

7 Comments

  1. bamo2000
    January 21, 2019 @ 10:09 am

    method one worked… thanls

    Reply

    • sunil
      February 5, 2019 @ 3:28 pm

      method one worked ……………….thanls

      Reply

  2. Daniel Lara
    January 21, 2019 @ 10:25 pm

    You literally saved me!, I tried all the methods that are around without expecting to be something Windows Update related, I hope they would include something that could point to this fix.

    Reply

  3. ADadmin
    January 23, 2019 @ 12:14 am

    Method one worked on my home network shares. I am an AD admin and tested this at work. The bug does not appear to affect AD members.

    Reply

  4. DJ
    January 28, 2019 @ 2:47 am

    Method one worked perfectly and saved me boatloads of time trying to pinpoint this, thank you, thank you, thank you!

    Reply

  5. Muhammad Mohsin Raza
    January 30, 2019 @ 1:39 pm

    Method one worked for me perfectly. Thanks

    Reply

  6. George
    January 31, 2019 @ 12:53 pm

    You are awesome. Method 1 worked perfectly. Thank you.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *