Cannot reliably run the file since the 10.1 version...

[ericb7799]

so ever since the update to most recent version I cannot get the file to run correctly. See the image for the error details but it is telling me that no matter what OS I use that the "build is not supported". The error in the image is from Windows 7 Ultimate SP-1 64bit, which I know is most definately supported. You may see that this was before the Windows 7 was activated as it is showing it under the "initial free period". Has just rebooted from a Recovery and now Win 7 makes me reactivate everytime I''ve recovered an OS installation. Is now activated but the error is unchanged. Also get the same error on my Windows 10 computer. In both cases have pulled up the .ini for UpdateGenerator and UpdateInstaller and have noted that majority of entries are showing as "Disabled" attempted to manually change everything to "Enabled" and save the file back to the folder. But it seems if that does work (rarely) the very next time I check it will get the same errors and again the .ini file will be mostly "Disabled".

IMG_0159.JPG

Screen Shot of error message on Win 7 Ult Sp-1 64bit

(111.51 KiB) Not downloaded yet

[ericb7799]

For additional clarification this is occurring after downloading the WSUSoffline10.1.zip file and then extracting to my update directory. In my case it is "c:\wu\wsusoffline". The error occurs usually when launching the Updategenerator.exe. there is not usually an.ini file showing until after I run the Updategenerator.exe at least once. I have been checking the .ini file when it does appear and I have noticed that regardless of my selections in the UpdateGenerator.exe menu, the .ini file will show most (if not all) options as "Disabled". Typically I only need the x64 versions and do not need the Office options. I do have a key for Office 2016 but I have not installed it yet. Before in previous versions of WSUSoffline I was downloading the updates for mulitple other OS (XP-64, Vista, Win 7, Win 8.1, and now Win 10 also) as I still have old OS that are on other disks/computers that i may try to update and keep running for as long as I can. I would typically just burn to DVD and then install from there on the individual OS's/machines with DVD. Now I cannot even get any of my OS to get the initial download of the updates because of the "medium neither supports your Windows or Office version" error on attempt to download. I have tried to manually replace "Disabled" with "Enabled" in the .ini file and it did seem to work a couple of times and I let it download the updates for about 6 hours or so. In that case once I had the updates I went to the client folder and tried to install them with the UpdateInstaller.exe and then getting the same "medium neither supports your Windows or Office version". I tried to do both options for the ISO files (I think I did end up with both the x86 and x64 versions) yet the error remains. Error is the same when try to install the downloaded options to another OS. Example: ON the Windows 10 tried both the normal way: download and then install by extracting the initial zip file to a clean update dir, then running the update generator but immediately get the "not supported" error. So then tried to just install a previously downloaded update file x64, but same exact error. In most cases, even if I try to manually change the .ini files to "Enabled" and then save it, as soon as I open it again it's back to mostly or completely being "Disabled". So I'm at a total loss....Of note I did try to download an earlier version of WSUS offline, (one of the 8.1 versions I think) and was able to get it to download and install the updates on my Windows 7 machine, but it does not support the Windows 10, so that is not working there. I don't think this or any previous version have worked for me on Windows 10. What could be causing all these issue? I was already a little skeptical because even in prior versions of this file I didnt think that is was applying the updates as it stated. So despite it saying it had downloaded and installed .net or essentials, I'd reboot and then check and some or many updates would be missing and not installed. Don't have any 3rd party anti-virus runnning and I've tinkered with turning off firewall and Windows update (which cant really be turned off totally in Win 10) with various levels of success but never total success in getting it to install correctly. Thanks...

[aker]

Please post a screenshot of UpdateGenerator, so I can see the settings.
Do you run a 64 bit (x64) or 32 bit (x86) Windows 10 installation?
It's normal, that many entries in UpdateGenerator.ini are disabled, as I'm sure you don't need updates for all languages of all Windows & Office versions.

[ericb7799]

I think I have at least for now, resolved the issue on the Windows 7 Ult computer. Seems to be related to our good old friends Windows Update and and dotnet 4.6 framework. Was doing some debriefing myself after a mess with a new .net 4.6 issue I ran into, and want to see what you guys think or if this is just coincidence. Started 2 days or so ago when all of a sudden win 7 ult 64 bit sp1 with . Net 4.6 started to fail with errors launching any program that requires 4.0 or above. Started getting the old dreaded "to run this application need to install .net 4.0.30319". The .net 4.6 was still showing as installed but both attempts to uninstall or repair install fail with non descriptive error akin to "something went wrong". All other logs make no mention related to it. After exhaustively searching for what had changed found that last batch of updates in wsus cab2 (?) installed kb3035583 which turns out to be the Windows 10 "important" and "automatic" update to install that pesky harrasser that reminds you to reserve or start download of win 10 from ms update. Problem being that it crashed and corrupted the existing .net4.6 while at the same time setting the default minimum allowable .net to what is currently for Win 10 at 4.6 only. So it was both blocking attempts to uninstall or repair the broken .net 4.6. The .net repair tool also fails. Then it Hijacked existing win 7 update so that only option in Win Update is to start downloading win 10 in background. Only option seems to be to totally delete Windows/system32/gwx.exe. Only then can you uninstall that update and only then can you uninstall .net 4.6. As soon as I did that and installed 4.5.2 everything is back to normal working order. I wonder how many people won't go that far or accidentally start the Win 10 download over their working win 7 os. Anyway just the nightmare I just woke up from and word of caution to others. You also need to hide that update if you don't want to "upgrade" to Win 10, because it will immediately try to re-install it as soon as you run Windows Update again.

Going to try to run the newer version of wsusoffline on the 10 machine later tonight. Hope that works also,

[ericb7799]

Here are some screenshots of the updategenerator and update installer ini and selection screens

[ericb7799]

I'm not exactly sure if any of the changes in the 10.2 had any effect. And to the previous question..all my OS are 64 bit and I don't download any of the x86 updates, yet it always still names the isos x86 x64 if I remember right. In any case ran it a couple of times and it is now working with no issues on the Windows 7 system. Everything actually seems to be running much better without .net4.6 and quite nice back to 4.5.2

[ericb7799]

issues seemed to be resolved since removing the Win 10 harrassment "update" on Windows 7. The Windows 10 system is also updating properly since the 10.2 wsus update.

[aker]

1) KB3035583 == Windows 10 ad-update (GWX)
Removing this update will remove the Icon from the tray and the message from Windows Update.
You are able to hide the update, but as MS regulary refreshes the package (at least 3 times as I've seen the update 3 times after hiding it), it will show up regulary.

2) You have to ask MS for finding out, why .NET 4.6 causes problems.

[ericb7799]

So I just got off the phone with both the Home users "Answer Desk" and then MSFT Technet Technical Support and neither would confirm what the KB3035583 actually does in relation to any .net installations.

Said I would have to pay $499 to "open a case" which is absolutely ridiculous when this is an "update" that without our knowledge was just changed from "optional" to "automatic" and will install if people aren't as tech savy. To stop it from installing one has to make sure to take Windows Update off of automatic and then every time you get a notification you need to check which updates it wants to install and manually hide that update. Once it is installed there is a whole lengthy procedure to get it removed correctly.


As far as I can tell it does affect the .net framework so that is seems to set the .net allowable minimum on Windows 7 to .net 4.6. So then the .net 4.6 has it's own set of issues and itself is not stable. When it inevitably has an issue comes up and gets damaged/corrupted you can no longer roll back to one of the .net 4.5 versions. Trying to run the .net 4.6 installer (any version tried so far) will either give an outright blocked installation message when you try or it will attempt to "repair" the .net 4.6 but fails every time..also nice that after it fails it gives the super helpful error message of "something went wrong" which in my opinion should just be replaced by a picture of a middle finger for all the help that is...way to go msft.. keep trying to sneak in the back door (pun intended) with all of us who are not real keen on moving from our (previously) working Windows 7 machines to this jacked up/unstable Windows 10 thing.


There is a reason we are still using Windows 7 and didn't go to Windows 8. What makes you think you can force people to accept this Windows 10 nightmare by trying every sneaky method in the book? I hope more people get wind of this kind of behavior. In my case I just bought an IMac, which previously I've never even considered...so way to go Windows...made me a Mac user now. I have a Windows 10 computer also BTW that is so messed up that immediately after doing the 20th (not kidding) "clean install" tells me I don't have "sufficient permissions" to save a .txt file to my desktop. going to have to file it in the "corporate recycling bin".....(ie: the trash) until msft can extricate their heads from their hind ends.

[boco]

I'm using a little tool called DWS (Destroy Windows Spying) which is designed to remove/block Telemetry (phoning home) but also removes the harassment updates in the process. Additionally it will disable phone-home tasks and block MS data collection servers (WinFW block and hosts).

Full Sources provided. Please search for it as I don't know if I'm allowed to link to that tool here.