New
#1471
I am NOT so sure. Hence did AI search.
Here is AI reply.
Update your Win 7 installation media
-
-
New #1472
The link to rg-adguard was for the correct filenames and the checksums/hashes, not as a download source for the ISO (though you can find those too). But you can verify them elsewhere. The ISO were available from MSDN channel for months but eventually MS took them down (like they did all other Windows 7 installation bits). The links direct from MS servers (which I downloaded myself when they were live using Windows ISO Downloader from HeiDoc.net) used to be:
https://download.microsoft.com/download/5/1/9/5195A765-3A41-4A72-87D8-200D897CBE21/7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_ULTIMATE_x64FRE_en-us.iso
MD5: 8ce237e3d43ccfb41bfe32ccd4420e10
SHA-1: 7cc76b0015220de956328fb934d61b710a94293d
https://download.microsoft.com/download/0/6/3/06365375-C346-4D65-87C7-EE41F55F736B/7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_PROFESSIONAL_x64FRE_en-us.iso
MD5: 262ff7318b375bdb70fdf84a3f6c3384
SHA-1: b3260ce8c339e13c4e6d327e1310b06c8e1402b0
https://download.microsoft.com/download/E/A/8/EA804D86-C3DF-4719-9966-6A66C9306598/7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_HOMEPREMIUM_x64FRE_en-us.iso
MD5: 89fc10690c99d14e3363d23b3e2f6033
SHA-1: c15bb9873548bd4a69371bc7966560c13162128c
https://download.microsoft.com/download/1/E/6/1E6B4803-DD2A-49DF-8468-69C0E6E36218/7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_ULTIMATE_x86FRE_en-us.iso
MD5: 23effc7708412e1ff4c1b3a935c1400e
SHA-1: 6f8791fbb4e883ff96b7ffc202640b0a8053d122
https://download.microsoft.com/download/C/0/6/C067D0CD-3785-4727-898E-60DC3120BB14/7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_PROFESSIONAL_x86FRE_en-us.iso
MD5: 01cea5b8cc7ff196331c5a8237dfc870
SHA-1: f1b6b81c6f6c7bab91dcaf711502706468b3d09a
https://download.microsoft.com/download/E/D/A/EDA6B508-7663-4E30-86F9-949932F443D0/7601.24214.180801-1700.win7sp1_ldr_escrow_CLIENT_HOMEPREMIUM_x86FRE_en-us.iso
MD5: 73807bd827432d75348092df86fb1b8d
SHA-1: 110674427b27f7216a95c4d659ae9f211c91fefd
links are getting parsed/truncated
- - - Updated - - -
Well the links can be found here. They are of course long dead but it shows they were direct from Microsoft. You can search the links themselves to find many discussions on them.Last edited by tcsenter; 2 Weeks Ago at 22:23.
-
-
New #1474
I don't think you provided enough specific detail for AI to 'think' you asked anything more than whether Microsoft more generally releases 32-bit and 64-bit products, or updates to them, through MSDN. Much of the content from MSDN was restricted access not publicly available, particularly the pages containing 'drop info' and discussion of binaries and downloads (even if the downloads themselves might not be restricted access). AI isn't going to have too much access to stuff that sat behind a paywall or restricted login access. The old MSDN was killed off, moved to Microsoft Docs a few years ago.
What's the point, of using it as a base ISO per my original question?
-
New #1475
Probably be ok. Try it and find out.
If you run 7updater.cmd without using simplix will just add sha2 usb3 and nvme support and a couple of more up to date net drivers
Unlike the usual ms isos they only contain one edition, which one do you want to use ?
You could probabaly export all the install.wim images into one and delete the sources\ei.cfg to make all editions available from one.
export pro into home premium install.wim
then export ult into home premium install.wim
then if you run 7updater.cmd and select * it will use the edition upgrade method to update all the images. Much quicker than one by one.
- - - Updated - - -
If you are not familiar with edition upgrade you can look through 7updater.cmd
for example mounted home premium image can be upgraded to Professional or Ultimate
dism.exe /Image:"mount directory" /Get-TargetEditions
e.g.
dism.exe /Image:"L:\mount" /Get-TargetEditions
dism.exe /Image:"mount directory" /Set-Edition:"edition name"
e.g.
dism.exe /Image:"L:\mount" /Set-Edition:"Professional"
Last edited by SIW2; 2 Weeks Ago at 03:46.
-
New #1476
OK so these ISOs come with NETFX 4.7.x installed as well as those telemetry and "Unsupported Hardware" notification updates if you try to run Windows 7 on CPU later than 6th gen (Skylake) or the equivalent from AMD, which I am using (AMD Ryzen 4500 and NVME drive).
I ran 7UPV64R without any flags to integrate just the USB 3.0, NVME, etc. NO add-ons or the Simplix UpdatePack. The resulting ISO booted and installed perfectly (and FAST), but not long after final loading of the desktop was met with the 'unsupported hardware' notification. However after running the December 2024 Simplix UpdatePack (had to run it twice to get all completed), I haven't received this notice at all, and Windows Updates seems to be offering the updates (non-ESU of course) still outstanding. Thanks!
After Simplix, Windows Update did offer KB3123479: "Deprecation of SHA-1 hashing algorithm for Microsoft root certificate program: January 12, 2016" as an outstanding update, which I applied. Not sure if that was supposed to already be installed (or superseded?) by either 7UPV64R or Simplix UpdatePack?
-
-
New #1478
-
New #1479
I have since perused a few discussions about them. Some are of the opinion it may be best not to use them since they've already been mucked with, had updates (lots of them) integrated or staged for installation. Whereas the various solutions for 'custom ISO building' have been developed around and assumed a 'clean' copy of the original bits (with SP1) released by MS. IOW, there is not a great amount of testing experience with them, so one will be blazing their own trail with them, in manner of speaking.
Having said that I have not encountered any issue. My Event Viewer logs look really good with very few errors (of significance), just the usual suspects you see on practically every darned Windows 7 installation. Not even that pesky 'unsupported hardware' notification anymore, though I'm not sure why unless Simplix removes it? Maybe Microsoft's little internal algorithm for when to show it is just giving me a false sense of security and will decide to popup again while I'm doing something important.
- - - Updated - - -
After applying onto x86 (32-bit) ISO, after installation I am getting a new context menu with CMD Prompt or Take Ownership as options? I see someone asked previously but that user did not reply back with clarity on what they did to solve the problem or prevent it. Is the official solution to prevent it by deleting the "softx86" or "softx64" reg file in BIN folder before running? Why doesn't this happen with 64-bit integrations? I always decline to install the 'enhanced menu' on all the builds tested so far but only notice it when integrating 32-bit installation media.Last edited by tcsenter; 1 Week Ago at 02:46.
-
Quote
Related Discussions