Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).

16 Comments

  1. Hari
    February 10, 2026 @ 7:05 am

    Method 1 worked for me too.
    Thank you so much for your blog and saving everyone time by providing the details steps.

    Reply

  2. bob
    October 27, 2025 @ 7:05 pm

    Thanks :) Method 1 worked

    Reply

  3. MARCELO BERGER
    July 8, 2025 @ 4:49 pm

    This was the only method that worked for me after countless different tutorials. thanks!

    Reply

  4. Juvani
    October 26, 2024 @ 7:55 am

    Thank you, Sir Konstatinos Tsoukalas. It has solved my problem using Method 1. May God bless you.

    Reply

  5. braa salahi
    June 7, 2024 @ 4:48 am

    I spent more than 3 years looking for a solution to this problem, and I finally found the solution from you, thank yo

    Reply

  6. maxi
    April 14, 2023 @ 3:12 pm

    solution n 1 worked perfectly! thank you very much!!!!!

    Reply

  7. Chris Jacobs
    April 10, 2023 @ 1:34 am

    Thank you so much! Method 1 finally worked and solved my issue. After searching the internet and microsoft website, this method was finally the one to work. Thank you.

    Reply

  8. Unforgiven
    March 31, 2023 @ 3:57 am

    same issue on win10pro.
    the first solution works for me too.
    i also was in situation the Matthew has mentioned about.
    i runed the windown update yesterday too.
    i called it windown intentional and not windows, because it let you down in every aspect.
    and look likes it causes too.
    i also suspect the malware, virus, PUA and rootkit.
    and scan with security softwares and problem still there.
    how lucky we are that we have you and find this fix.
    everybody knows that windown s*cks.
    thanks for the guide that nanosoft itself can't provide for us.

    Reply

  9. fryser007
    March 19, 2023 @ 3:03 am

    Thank you 1st answer worked!

    Reply

  10. D Smith
    February 8, 2023 @ 7:29 am

    The registry edit fixed this problem EASILY. Thank you so much.

    Reply

  11. Havanna
    February 28, 2022 @ 12:25 am

    1st Solution Worked. I despise windows 10, Required however for my job 😭

    Reply

  12. Mark
    November 8, 2021 @ 3:52 pm

    Looks like this problem plagues win11 as well, since win11 is the same ole' pig as win10 except with different color lipstick, this fix still works. :-)

    Reply

  13. Mustafa
    June 1, 2021 @ 4:22 am

    U sir just made my day thank you sooooooo much

    Reply

  14. Jonny
    March 18, 2021 @ 2:24 pm

    crypo services as network service fixed it for me thanks

    Reply

  15. Matthew Crandall
    February 11, 2021 @ 11:29 am

    Encountered this yesterday (Feb. 11, 2021) on a computer that was being used as a cash register w/ POS software. Was at first convinced that it had a damaged sdd drive, then on second thought that it was infected with malware. But in the end the situation was entirely resolved through "Method 1" above. A follow-up hd scan found no damage, and a full virus scan found no virus. Of note, windows update had just installed updates on the computer the night before… so i'm guessing winblows update caused the damage.

    Reply

  16. Lawrence
    September 27, 2020 @ 8:56 am

    You are a saviour, the EnableLUA=0 fixed it! Just been forced to infect my PC with win 10 and it's a most horrible experience, everything and every step is a battle/research just for making sh*t work, the sh*t that can be fixed, it is, because some can't. It's like a digital house of horrors, behind every click there is something dysfunctional or that cannot be done normally or at all.

    Reply

Leave a Reply

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