Author Topic: Windows 7 Component Store Cleanup - Rebase  (Read 153296 times)

June 11, 2021, 12:46 PM
Reply #460
  • Global Moderator
  • *****
  • Posts: 889
  • Gender: Male

Well, I didn't know this package. But I'm afraid it might impede the installation of future updates.
I'll try to upload some new versions soon.

Note that I left Grau du Roi this morning. I hope you enjoyed the photos on the forum.
/ResetBase might kill system reset feature but /startcomponentcleanup will not impede win updates/upgrades.
You're welcome. I'm glad you understood it the first time. If you didn't I don't know how to re-phrase them in a simple way. haha..

At first I didn't get it. Then I started playing around with it until it finally made sense.

Did you say you used ESD to put this ISO together? If so, what exactly does that mean? What ever you did it works great. Both the desktop and the lappie upgraded without a hitch. How'd you accomplish this?
Wim file was around 5.62GB while ESD size was 2.97GB and ESD conversion/de-conversion is time consuming and memory/cpu intensive  and approximately takes 1-2hrs to complete depending on updates.
This time I used Win10UI from abbodi's Batutils scripts along Wintoolkit (integrate edge, FSViewer, few regtweaks, hibernation disabling, show all power options, dx9 etc..) and NTLite(Remove unwanted Appx, assembly files etc).
When I use Wintoolkit/NTlite it takes atleast 3 hrs to manually slipstream updates in install.wim and boot.wim and re-check in VBox VM.
With Win10UI's ini file I made a base OS with slipstreamed updates, unchecked netfx35 integration, skipped ISO/ESD creation. So, it took 15-30 mins to update all editions. I used Wintoolkit/Ntlite to add programs and cleanup basically reducing my 6-8hrs workload.

June 11, 2021, 12:58 PM
Reply #461

June 11, 2021, 09:29 PM
Reply #462
  • Global Moderator
  • *****
  • Posts: 2269
  • Gender: Male
Vasu: Whatever you did on that ISO it worked perfectly. This is the only Windows upgrade ISO that worked flawlessly on both the desktop and the laptop.

You said hashes are necessary because the ISP might alter the ISO. Wouldn't they also alter the small hash file too?

June 13, 2021, 01:15 PM
Reply #463
  • Global Moderator
  • *****
  • Posts: 889
  • Gender: Male
Vasu: Whatever you did on that ISO it worked perfectly. This is the only Windows upgrade ISO that worked flawlessly on both the desktop and the laptop.

You said hashes are necessary because the ISP might alter the ISO. Wouldn't they also alter the small hash file too?
Thanks.
Yes indeed but normal users were frustrated even with double hash checks for password protected archive and files itself, so I refrained from adding it. Then again mega.nz has encryption and file checks anyway. Next time, I will add hashes for all files so that it can be 100% ensured it is authentic.

June 14, 2021, 09:58 PM
Reply #464
  • Global Moderator
  • *****
  • Posts: 2269
  • Gender: Male
Yes indeed but normal users were frustrated even with double hash checks for password protected archive and files itself, so I refrained from adding it. Then again mega.nz has encryption and file checks anyway. Next time, I will add hashes for all files so that it can be 100% ensured it is authentic.

Aren't you already doing that? Has your new ISP or anybody else interfered with anything you've uploaded, including the small hash file? I'm asking because if I wanted to somehow alter your upload, I do that and then create a new hash file.

Another thing: it appears that with 21H1 Micro$shaft has squashed the failed upgrade bug. Just right now Windows update notified me of an important update. It installed perfectly. Not only that, other optional cumulative and driver updates also installed without the slightest hiccup. This is the first time in quite a while I've installed updates from Micro$shaft flawlessly and with no headaches. So far 21H1 is rock solid. For this reason I urge all you guys to upgrade to it, the sooner the better.

June 16, 2021, 02:02 PM
Reply #465
  • Global Moderator
  • *****
  • Posts: 889
  • Gender: Male
Yes indeed but normal users were frustrated even with double hash checks for password protected archive and files itself, so I refrained from adding it. Then again mega.nz has encryption and file checks anyway. Next time, I will add hashes for all files so that it can be 100% ensured it is authentic.

Aren't you already doing that? Has your new ISP or anybody else interfered with anything you've uploaded, including the small hash file? I'm asking because if I wanted to somehow alter your upload, I do that and then create a new hash file.

Another thing: it appears that with 21H1 Micro$shaft has squashed the failed upgrade bug. Just right now Windows update notified me of an important update. It installed perfectly. Not only that, other optional cumulative and driver updates also installed without the slightest hiccup. This is the first time in quite a while I've installed updates from Micro$shaft flawlessly and with no headaches. So far 21H1 is rock solid. For this reason I urge all you guys to upgrade to it, the sooner the better.
I'm using mobile data as hotspot nowadays so till now they haven't interfered. maybe I'll add that file you asked since its a small hash files and will provide more authenticity.
20H1 and 20H2 had upgrade blocks from synaptics and conexant audio/touchpad drivers I use on lenovo's and dell.
Since 1909 was EOL, I had to make a jump to 21H1 directly.

June 16, 2021, 08:55 PM
Reply #466
  • Global Moderator
  • *****
  • Posts: 2269
  • Gender: Male
I said M$ had squashed the upgrade bug. Not completely. The optional cumulative update did not update on my laptop, although everything else did. They've improved it but obviously haven't fixed it completely. Maybe Windows 11 will bring some more fixes with it.