Solved Reinstalling Win 7

[msalton1]

Success!

I also used to use the:

[1] - KB3020369 - Servicing Stack Update - April 2015.
[2] - KB3125574 - Convenience Rollup Package - May 2016.
[3] - KB3172605 - Functional Update Rollup [THIS ONE IS IMPORTANT] - July 2016.
[4] - KB3179573 - Functional Update Rollup - August 2016.

I installed the numbered updates you list here, then ran Dism++ and it downloaded and installed.
It didn't take long once DISM++ started...maybe 30 mins total. It installed all but 38 updates, which included about 30 updates (ranging from 2012 on), 2 rollups (one of which was for IE 11, which I don't really use, but may install anyway) and 6 feature packs (Net Framework updates).


Does the number of updates that weren't installed sound about right? Also, what about the Net Framework updates? Shouldn't some of those be installed (I think Quickbooks requires a certain version...?).

 

[Paul Black]

Hi msalton1,

Just tried again. The odd thing is that afterwards, I plugged my existing system drive (and other devices) back in and booted, then decided to try Dism++ on the same machine with my daily hardware configuration. Only had a few updates, but Dism++ connected, downloaded and installed.

Just a thought for the problem (new install) SSD...should I leave the Dism++ default updates checked? Should I start with an older update that might be causing an issue if not installed first?

Are you saying that you have been trying to run DISM++ on two different HDD's [that have different configurations]?

I only ever install the updates that the DISM++ Scan finds and are ticked. I usually run DISM++ two or three times until there are no more updates available. Never install any of the orange updates as there is a problem with them or they contain telemetry etc.

[7] It warns you if an update:

• Includes telemetry.
• Has known issues with certain hardware.
• Needs exclusive access.
• Is suspect.
• Your OS doesn't need it.
• Has any other known issues.

I hope this helps!

 

[Paul Black]

Hi msalton1,

If Dism++ isn't going to do the job, I guess I'll have to do it that 'old fashioned way'.

First of all, I have done WU on a clean install many many times before using a variety of methods. As you have probably gathered from my previous posts, the method that I find the most thorough, quickest and easiest for purely WU's is DISM++. The best and easiest method for WU's and drivers is 7UPDATER [see below].

Here is a quick list of some of the methods [because I could write pages on this] I have used after a clean install:

• Run WU. The problem with doing it this way [I found] is the amount of time needed to download and install all the updates, not to mention the numerous restarts required. You also need to scrutinise each and every update in case of telemetry etc, although not so much these days! I only really installed the critical updates, and maybe some of the system security updates, never any important or recommended updates or hotfixes.
• Manually downloaded the .msu [Windows Update Standalone Installer] files for the 4 updates in my post #18 and then ran DISM++.
• Manually downloaded the .msu [Windows Update Standalone Installer] files. These included the 4 updates in my post #18, and the Security-Only-Updates for each month. I then installed each of these in the correct order manually. I then run WU for anything else that I deemed important enough to install.
• I did exactly as I have stated above. This time however, I put all the files into a folder and numbered each of them in the order that they were to be installed. I started with a Win 7 SP1 ISO. I wrote a DISM based script that integrated all the updates into the ISO [install.wim] and then created a new installation USB [it had to be a USB because after the integration the install.wim was to big to fit onto a DVD]. Basically, the script created a folder that was used to mount the install.wim file, it then mounted the install.wim file into that newly created folder, it then integrated all the .msu update files, it then saved and un-mounted the install.wim file committing all the changes made, it then cleaned up any leftovers, it then deleted the folder that was be used to mount the install.wim file, and finally, it created a new ISO that had ALL the integrated updates ready for burning to a USB.
• I used a utility called 7UPDATER, created and written by SIW2 => Update your Win 7 installation media. This also creates an integrated updated ISO and also has the ability to integrate drivers into the Bootx64 and Installx64 folders. It uses a method that includes the SIMPLIX update pack.
• I used DISM++. I have already covered this many times in other posts!

Paul, does your post #18 contain all the steps I'll need to get current? Is there a guide with a certain order, etc? Is there a list of updates I'll need to uninstall after (i.e., the 'phone-home' updates)? I'd like to do this the right way to avoid any issues down the line.

No, the list isn't complete. There is a post of mine somewhere on this forum that covers what updates are needed and what order etc they need to be installed in!

I hope this helps!

 

[msalton1]

Are you saying that you have been trying to run DISM++ on two different HDD's [that have different configurations]?

No. Given the issues I was having, I plugged my "existing install" HD back into the system and tried running Dism++ and it downloaded and installed an update. At that time, I used the method quoted below. After installing those 4 updates manually (in the order you posted), I then ran Dism++ and it was then able to download and install all of the 'checked' (default Dism++ updates)

Hi msalton1,

Here is a quick list of some of the methods [because I could write pages on this] I have used after a clean install:

• Manually downloaded the .msu [Windows Update Standalone Installer] files for the 4 updates in my post #18 and then ran DISM++.

This is what I did ^ (as per my previous [#21] post). Dism++ just didn't want to work until these ^ 4 updates were installed.


I seem to be on track now and will finish setting the drive up for my business in the next week or so. My next step is to run Dism++ again a few more times, as you suggest.


Thanks very much for hanging in there to help through the process, and definitely for pointing me to Dism++, which, although initially problematic, made the update process much easier.


In fact, could Dism++ be employed as a regular manual update tool? It would seem easier than delaying every update until I can research for any issues. Seems like a great utility.


Again, your help has been much appreciated! Can't give you more rep ATM, but thanks!

 

[Paul Black]

Hi msalton1,

No. Given the issues I was having, I plugged my "existing install" HD back into the system and tried running Dism++ and it downloaded and installed an update. At that time, I used the method quoted below. After installing those 4 updates manually (in the order you posted), I then ran Dism++ and it was then able to download and install all of the 'checked' (default Dism++ updates).

This is what I did ^ (as per my previous [#21] post). Dism++ just didn't want to work until these ^ 4 updates were installed.

Very strange, I never had that happen to me!

My next step is to run Dism++ again a few more times, as you suggest.

That is what I would do, it will make sure that the OS is pretty much upto date then!

Thanks very much for hanging in there to help through the process, and definitely for pointing me to Dism++, which, although initially problematic, made the update process much easier.

You are very welcome!

In fact, could Dism++ be employed as a regular manual update tool? It would seem easier than delaying every update until I can research for any issues. Seems like a great utility.

That is the way I do it. I usually don't run it until the day BEFORE Patch Tuesday. That way, any amendments/re-updates are all sorted [we can all but hope]!

Again, your help has been much appreciated! Can't give you more rep ATM, but thanks!

Again, you are very welcome!

 

[msalton1]

One thing I note is missing from Dism++ is an option to find and uninstall unwanted updates (i.e., telemtry, etc). Is there an option that I'm missing? What is the most efficient way to accomplish this?

 

[Paul Black]

Hi msalton1,

One thing I note is missing from Dism++ is an option to find and uninstall unwanted updates (i.e., telemtry, etc). Is there an option that I'm missing? What is the most efficient way to accomplish this?

If you used DISM++ to install the WU's [Windows Updates], then as long as you didn't install ANY of the ORANGE highlighted ones then you shouldn't have any Telemetry updates.

I hope this helps!

 

[msalton1]

Hi msalton1,



If you used DISM++ to install the WU's [Windows Updates], then as long as you didn't install ANY of the ORANGE highlighted ones then you shouldn't have any Telemetry updates.

I hope this helps!

Sorry - should have been more clear. I'm not asking for a new install, but rather for existing installs of several machines here. I've tried to keep up, but most of these installs are 4 to 5 years old and may include some of the unwanted updates.

 

[msalton1]

BTW, I've postponed the 'new install to the new SSD' until I update hardware on key systems in preparation for MS drop of Win 7 support. No point in clean installing to a machine that will need it again for new hardware.

 

[SIW2]

Dism++ can uninstall updates. You will need to tell it which you don't want.

There is a suggested list here:
The following updates are undesirable and excluded:

KB971033- x86-x64 (Update for Windows Activation Verification Technologies)
KB2952664- x86-x64 (System Compatibility Update to upgrade to Windows 10)
KB2977759- x86-x64 (Diagnostics compatibility problems for the transition to Windows 10)
KB3021917- x86-x64 (System diagnostics and telemetry for switching to Windows 10)
KB3035583- x86-x64 (Update installs the application "Get Windows 10")
KB3068708- x86-x64 (Update to improve the quality and diagnostics of telemetry)
KB3075249 -x86-x64 (The update adds telemetry points to the consent.exe file)
KB3080149 -x86-x64 (Update for CEIP and telemetry diagnostics)
KB3081954 -x86-x64 (Update to improve working folders and telemetry)
KB3123862- x86-x64 (Updated ability to upgrade to Windows 10)
KB3139923 -x86-x64 (The update adds telemetry points to the consent.exe file)
KB3150513- x86-x64 (Updated Configuration for Diagnostic Compatibility)
KB3161608 -x86-x64 (Update adds telemetry points to the consent.exe file)
KB3163589- x86-x64 (Message about work under the management of an outdated version of Windows)
KB3172605 -x86-x64 (The update adds telemetry points to the consent.exe file)
KB3173040- x86-x64 (Notification of the expiration of the upgrade to Windows 10)

Google Translate

 

[msalton1]

Dism++ can uninstall updates. You will need to tell it which you don't want.

There is a suggested list here:
The following updates are undesirable and excluded:

KB971033- x86-x64 (Update for Windows Activation Verification Technologies)
KB2952664- x86-x64 (System Compatibility Update to upgrade to Windows 10)
KB2977759- x86-x64 (Diagnostics compatibility problems for the transition to Windows 10)
KB3021917- x86-x64 (System diagnostics and telemetry for switching to Windows 10)
KB3035583- x86-x64 (Update installs the application "Get Windows 10")
KB3068708- x86-x64 (Update to improve the quality and diagnostics of telemetry)
KB3075249 -x86-x64 (The update adds telemetry points to the consent.exe file)
KB3080149 -x86-x64 (Update for CEIP and telemetry diagnostics)
KB3081954 -x86-x64 (Update to improve working folders and telemetry)
KB3123862- x86-x64 (Updated ability to upgrade to Windows 10)
KB3139923 -x86-x64 (The update adds telemetry points to the consent.exe file)
KB3150513- x86-x64 (Updated Configuration for Diagnostic Compatibility)
KB3161608 -x86-x64 (Update adds telemetry points to the consent.exe file)
KB3163589- x86-x64 (Message about work under the management of an outdated version of Windows)
KB3172605 -x86-x64 (The update adds telemetry points to the consent.exe file)
KB3173040- x86-x64 (Notification of the expiration of the upgrade to Windows 10)

Much appreciated. Thanks.