Simplix Pack to update Live Win7 System/ Integrate hotfixes into Win7 distribution

I run updatepack7R2, obtained UpdatePack7R2-23.4.11.exe to update my existing Windows 7 (with .Net4.8).

If I add new *.WA files (dotNetFx48_20230214_x64.WA) into the fold of UpdatePack7R2-23.4.11.exe, how to make it to do *.WA update same time?


I did test, couldn't see *.WA updated (still .Net4.8. no .Net 4.8.4614.10 something) when running UpdatePack7R2-23.4.11.

Thanks,

 

I need to run updatepack7R2(1MB) to obtain UpdatePack7R2-23.4.11.exe(830MB).

put the WA file, before or after above run?

If before, means, run updatepack7R2 (1MB) with WA file, to obtain UpdatePack7R2-23.4.11.exe (830MB). then run UpdatePack7R2-23.4.11.exe(830MB) alone.
If after, means, run UpdatePack7R2-23.4.11.exe(830MB) with WA file. <-- I did this way. and UpdatePack7.log didn't show installation of dotNetFx48_20230214_x64.WA.

Thanks,

 

Doesn't matter at all.

Rename the downloaded pack(830MB) to "++--" and run it as admin. Make sure the addons are in the same folder and the path to the folder is as simple as possible(no fancy symbols, spaces, etc.).

 

Let me try again,

Thanks,

 

interesting,

your way "++--" working. the popping-up message tells me its running. The update is NOT done yet, taking hours already.
(it failed 1-2 times when boot, I had to go repair)


Thanks,

 

If you need to run UpdatePack7R2-23.4.11.exe on a Windows 7 live system, you first need to rename it:

UpdatePack7R2--++.exe

 

Again, all you need is ++-- or --++ as the name of the .exe. Nothing more.

You need a clean install. Instead of trying to update the current install, offline update an iso and just use it for clean install.

 

I didn't know that.

my 1st try was using plain file name and failing.

I am moving back Windows 11 to 7 on some PCs. so have to do this task. I just got 1st PC updated properly following your tip (++--).

 

You don't 'need' to rename it to --++ or whatever. This is just the silent switch. (=it will reboot at the end without asking you). You can use it if you find it useful or you can leave it be if you want to have more control over when your system reboots. Its totally your choice.

 

1. Click the updatepack.exe
2. Press F2
3. Type --++
4. Press Enter
5. Run as admin

For the purposes of updating a live system, this is the least amount of hassle. That's the only reason I advise to just rename the .exe to --++ or ++--. It's simpler, instead of having people tunnel the idea that the updatepack needs to have a certain specific name.
Otherwise, if you know what you're doing, by all means go full meme mode and rename the pack to Update--Pack++7R2.exe and have at it.

For offline integration:
1. Put sp1 media refresh iso, pack and addons in the same folder
2. Drag&drop the iso to the updatepack.exe
3. Let it work

 

Well it does ask you at the end to Restart now or later. A bit hard to miss it in my opinion. I find this more newbie friendly than running the update with the silent switch and potentially loose any unsaved document etc. Ofcourse it is a bad practice to be working on anything during an update like this but not everyone knows this..
Anyway this has gone a bit off topic already.

 

Not sure if this is the place to report errors/bugs and whatnot, but reading through some posts here at the end and might give the ++-- thing a go... and add some .WA files because that's a very nice feature! Anyways...

I got caught in a boot loop installing it on a live system with the normal filename. Didn't have system restore enabled, which could have saved me a massive headache of mandatory data backup and a clean install.

Initially, I thought it had something to do with having custom themes enabled and a custom boot screen and logon screen. But after doing a clean install, I ran Simplix (using /Reboot /Silent /NoUSB), rebooted, and everything seemed fine. I have an old nForce4 board (which I believe was made for Vista). Installed the 15.49 Nvidia chipset drivers for it... Boot loop! I get halfway through the Win7 boot screen and a bsod pops up for a split second (not long enough to read) and a restart.

Before using system restore via startup repair in WinRE (successfully), I noticed there were 51 Windows Update entries installed. After system restore, I was left with 49. After that I was able to restart, install video and audio drivers (omiting the chipset driver), and the system seems stable thus far.

Kind of wondering if 51 updates is what I should be seeing. And if I should just clean install using the ++-- addition before I go any further. Maybe omiting the chipset drivers again, since they only install Away Mode (whatever that is), Storage Drivers (storage seems fine without it), and a useless Forceware Ethernet Manager network gui.


Edit: According to the simplix.info page, the --++ modifiers are basically a sort of shortcut to using the /Silent and /Reboot switches. Which I used for my installation process. So, I find it odd that I got stuck in a boot loop. I suppose it may be my chipset driver, though I have no idea what exactly triggers the startup error.

I suppose I could test each driver option during the chipset driver installation to narrow down exactly which option triggers it. Or find out if the entire 15.49 Nvidia package itself causes it. If it might be of any use to others. Hopefully the installation of resource modifier apps for custom themes doesn't produce the same issue...

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

thank you

 

You need to login to view this posts content.