You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -8,7 +8,7 @@ I uploaded a pre-compiled zip file to the Internet on 6/2/2015, a day after KB30
I created this in Visual Studio 2005. (yes, I know, it's all I had) To launch the project in Visual Studio, just click on idw_winX.sln. The main C++ file is */I Don't Want Windows 10/I Don't Want Windows 10.cpp*.
## How it Works
In the main C++ file, the program makes sure it's not being run on any Windows other than Windows 7 and Windows 8.1, and makes sure it's not being run under WoW64 in 64-bit Windows. (See issues section of this readme) The program then executes a system() call to *wusa /uninstall /kb:3035583* to finally uninstall the GWX update.
In the main C++ file, the program makes sure it's not being run on any Windows other than Windows 7 and Windows 8.1, and makes sure that if it's being run under WoW64 to disable file system redirection. The program then executes a system() call to *wusa /uninstall /kb:3035583* to finally uninstall the GWX update.
## Issues
The two major issues I have encountered with this code is that it can't run under WoW64 because for some reason, *%windir%\sysnative\wusa.exe* does not exist. The solution for this is that we have to ship both x86 and x64 bianaries, but I will continue to try to fix this so we only have to ship x86 bianaries. The other main issue I've been having is that for the life of me I can't get a message box to spawn. The two main scenarios where we would want a message box to spawn would be when the x86 bianary is being run from x64 or if the user is using an unsupported version of Windows. As a tempoary solution, I just echoed the message into a cmd window, but we should try to get this fixed as soon as possible.
The main issue I've been having is that for the life of me I can't get a message box to spawn. The main scenario where we would want a message box to spawn would be if the user is using an unsupported version of Windows. As a tempoary solution, I just echoed the message into a cmd window, but we should try to get this fixed as soon as possible.
