rn10950 Posted June 11, 2015 Author Posted June 11, 2015 (edited) I keep getting VS2005 build time errors in Wuapi.h By the way, Visual Studio 2015 Community Edition RC is available, and it's free. -Noel I can't use VS2015 because I am running Win2k3 on my main machine, and just have Win7 and 10 VMs. Plus, I need 98SE compatability, and VS2005 is the last version to support 98SE and the only to support both 98SE and x64. There are articles from 2004 talking about Wuapi.h so it's probably an issue on my end. Edited June 11, 2015 by rn10950
Glenn9999 Posted June 11, 2015 Posted June 11, 2015 There are articles from 2004 talking about Wuapi.h so it's probably an issue on my end. WUAPI was phased in with Windows XP (and maybe 2000?), so VS2005 should handle it just fine.
rn10950 Posted June 12, 2015 Author Posted June 12, 2015 Does anyone know the User Account name that Windows Update uses in 7 and 8.1 so I can deny it write permissions to \WINDOWS\System32\GWX?
rn10950 Posted June 15, 2015 Author Posted June 15, 2015 Sorry it's taking so long for v3.0, but I just can't get command line flags in MFC. I tried using many different code snippets dating all the way back to 1997 but every one I try either doesn't compile or doesn't work. If anyone has any ideas to put me in the right direction that would be amazing. This method is what I'm trying to get working now, and this is my implementation, but I keep getting a "error C2664: 'atoi' : cannot convert parameter 1 from 'CString' to 'const char *' " error at line 26.
dencorso Posted June 15, 2015 Posted June 15, 2015 Try to do an explicit type recast, from the type it says it cannot convert to the one the function requires. What the compiler is saying is that it refuses to convert those types implicitly.
NoelC Posted June 16, 2015 Posted June 16, 2015 ...which (to be explicit) will select an operator within the CString class that will provide a pointer to a char. -Noel
rn10950 Posted June 16, 2015 Author Posted June 16, 2015 I figured out the issue, and it compiles now, all I need to do is get it to work... Basically I was using 1997 ANSI code in a Unicode compiler, I set the compiler to ANSI and changed some of the Unicode functions to their ANSI equivalents and it compiles now. It should take me about a day to get all the features I planned working and the code cleaned up for a v3.0 release.
rn10950 Posted June 18, 2015 Author Posted June 18, 2015 Version 3.0 is here! Here are the changes in this release:Fixes the MessageBox problem - I had to move the code around a little bit.Kills GWX.EXE after update removal - logical decision.Has command-line support - read the readme file on the GitHub project homepage for more information.Major code re-writes - see bullet one.As usual, Thank You to anyone here that helped me with this release. The next one will be a tough one. 1
bphlpt Posted June 18, 2015 Posted June 18, 2015 Thanks! As dencorso and others have mentioned, here's hoping that v4 will include the ability to select which of the Windows 10 related updates listed here that the user would like removed, killed where appropriate, and hidden so you won't be bothered by them again. Cheers and Regards
Kelsenellenelvian Posted June 23, 2015 Posted June 23, 2015 I used this and was quite impressed with it's effectiveness, However, I also found a problem, the update was re-offered right after reboot. Is there a way to "fake" the entries so that it looks installed to WU? Or even to block the offending update all together?
NoelC Posted June 23, 2015 Posted June 23, 2015 You do know about hiding updates, right? Right click on an offered update and choose Hide. -Noel
Kelsenellenelvian Posted June 23, 2015 Posted June 23, 2015 It's part of asking for switches with it. I want a easier more elegant solution to the whole POS removal...
bphlpt Posted June 23, 2015 Posted June 23, 2015 ie: .. the ability to select which of the Windows 10 related updates listed here that the user would like removed, killed where appropriate, and hidden so you won't be bothered by them again. Cheers and Regards
JorgeA Posted June 24, 2015 Posted June 24, 2015 Once this tool is ready to go, the key will be to spread the word somehow. People can't benefit from it if they don't know about it. Would it be possible to, say, get it listed on the BetaNews file forum? --JorgeA
11ryanc Posted July 1, 2015 Posted July 1, 2015 Does this tool put a block on the updates from being acquired? Or is it only an aid to systems infected?My last update run was about a week ago. Thus far I haven't encounted it, but I'd rather not wait for it either. Hoping to find a solution before something bad happens 1st -Thanks
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now