Microsoft will remove the ISOs for Windows 10 and Windows 11 24H2 by 14 October 2025. Therefore, it is advisable to download the ISOs for your current language and store them safely in an easily accessible location.
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
On 16/9/2025 10:30 am, Jack wrote:
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
I don't quite use online storage. Save those files offline, zipped to act as error-checking! :)
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing
them.
I don't quite use online storage. Save those files offline, zipped to
act as error-checking! :)
Why not? Did you know that a Chinese company called TeraBox can give you
1TB of storage for free? I just created an account and uploaded a file
to test it out. The upload speed might not be adequate, but it is a free service.
Microsoft will remove the ISOs for Windows 10 and Windows 11 24H2 by 14 October 2025. Therefore, it is advisable to download the ISOs for your current language and store them safely in an easily accessible location.
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
On 16/09/2025 16:08, Mr. Man-wai Chang wrote:
I don't quite use online storage. Save those files offline, zipped to
act as error-checking! :)
Why not? Did you know that a Chinese company called TeraBox can give you
1TB of storage for free? I just created an account and uploaded a file
to test it out. The upload speed might not be adequate, but it is a free service.
On 9/15/2025 10:30 PM, Jack wrote:
Microsoft will remove the ISOs for Windows 10 and Windows 11 24H2 by 14
October 2025. Therefore, it is advisable to download the ISOs for your
current language and store them safely in an easily accessible location.
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
I have a USB media of 11 24H2, in case of an emergency need to reinstall, but it will be replaced with 25H2 as soon as Microsoft pushes it through Windows Update to me, that will tell me my device is considered ready for the new build.
Microsoft will remove the ISOs for Windows 10 and Windows 11 24H2 by 14 >October 2025. Therefore, it is advisable to download the ISOs for your >current language and store them safely in an easily accessible location.
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
On Tue, 16 Sep 2025 02:30:00 +0000, Jack <Jack@invalid.invalid> wrote:
Microsoft will remove the ISOs for Windows 10 and Windows 11 24H2 by 14
October 2025. Therefore, it is advisable to download the ISOs for your
current language and store them safely in an easily accessible location.
Ideally, zip and password-protect them in case you decide to store them
in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
Where and how does one get them?
On 2025/9/18 3:31:13, Joel W. Crump wrote:
On 9/17/2025 10:12 PM, Paul wrote:
On Wed, 9/17/2025 5:32 PM, Joel W. Crump wrote:
On 9/15/2025 10:30 PM, Jack wrote:
Microsoft will remove the ISOs for Windows 10 and Windows 11 24H2 by 14 >>>>> October 2025. Therefore, it is advisable to download the ISOs for your >>>>> current language and store them safely in an easily accessible location. >>>>>
Ideally, zip and password-protect them in case you decide to store them >>>>> in Google Drive and/or OneDrive (like me), to prevent Microsoft and
Google from mistakenly identifying them as pirated files and removing them.
I have a USB media of 11 24H2, in case of an emergency need to reinstall, but it will be replaced with 25H2 as soon as Microsoft pushes it through Windows Update to me, that will tell me my device is considered ready for the new build.
It makes more sense to store them as ISO files, as you can make
a USB stick from an ISO file, later on. The ISO can be re-purposed,
which for me is why they are a preferred format.
I've often wondered, especially if the "emergency need to reinstall" is
the reason, why people seek to obtain ISOs, rather than make images; for
me, the thought of having to do a reinstall of the OS, including hunting
for the key data, then all my software (including keys), then
reconfiguring both the OS and software to how I has them, is horrendous.
I could understand people wanting the ISOs if they intend to create
_new_ machines.
Of course, for people who do not separate user-created data from
OS/software, imaging may create unrealistically huge image files (I do
keep them mostly separate; the last image from my Windows 7-32 C: is
about 20G [may be gently compressed, I can't remember], and my C: under
10-64 is currently about 59G [uncompressed obviously]).
[]
I'm fine with 24H2 until 25H2 is pushed by Windows Update. My days ofSame here re the obsessing; even towards the end of Windows 7, I was
obsessing over stuff like that are past. If I really wanted to control
everything I wouldn't even run Windows at all, but Linux, but I've been
enjoying Windows again.
finding fewer and fewer things in the "up"grades that were adding things
I wanted or even needed, and were patches to things I never used. OK,
there's always the FUD security aspect. But I'd say anyone thinking of
using ISOs is savvy enough to be safe even without the latest versions
in that respect. (Yes, famous last words I know.)
Daniel70 wrote:
When I brought this Desktop, it already had Win-11 installed .... so I don't have an .iso file.
Can I create an .iso file from what I've got ... or am I out of luck??
You can download .ISOs or make USB sticks using the Media Creation Tool.
<https://www.microsoft.com/en-gb/software-download/windows11>
I've often wondered, especially if the "emergency need to reinstall" is
the reason, why people seek to obtain ISOs, rather than make images; for
me, the thought of having to do a reinstall of the OS, including hunting
for the key data, then all my software (including keys), then
reconfiguring both the OS and software to how I has them, is horrendous.
I could understand people wanting the ISOs if they intend to create
_new_ machines.
When I brought this Desktop, it already had Win-11 installed .... so I
don't have an .iso file.
It has been updated over the last twelve months or so. And, of course,
I've added programs that I use, as well.
Can I create an .iso file from what I've got ... or am I out of luck??
On 2025/9/18 11:26:22, Daniel70 wrote:
When I brought this Desktop, it already had Win-11 installed .... so I
don't have an .iso file.
It has been updated over the last twelve months or so. And, of course,
I've added programs that I use, as well.
Can I create an .iso file from what I've got ... or am I out of luck??
I don't know if you can make a .iso that includes other softwares you've installed; I think not, but it's not an area I'm familiar with.
I think you'd do better with an image, which would in the event of
disaster (drive failure, ransomware) let you restore to the state you
are (or were when you made the image). (With all the softwares
configured as they are.)
There are several utilities that will make the image - Paul and I like Macrium, but the latest version has moved to subscriptionware - but you should still be able to find the free version, which I think so far
works with W11 (Paul can say which version you need). Alternatives are
EaseUS and Acronis, I think - maybe others too.
If you do go the image route, it helps to keep user-created data on a different partition (or drive) - simply to keep the size of the image
file down. (you should still back up your data too of course, but that doesn't _need_ an image - any sort of backup will work, even just
copying. I use FreeFileSync, that way I don't need to copy what hasn't changed [though I should, occasionally].)
Andy Burns <usenet@andyburns.uk> wrote:
Daniel70 wrote:
When I brought this Desktop, it already had Win-11 installed .... so I
don't have an .iso file.
Can I create an .iso file from what I've got ... or am I out of luck??
You can download .ISOs or make USB sticks using the Media Creation Tool.
<https://www.microsoft.com/en-gb/software-download/windows11>
But the OP ('Jack') says this well known download capability is going
away by October 14 (also for Windows 10). Is he just talking FUD?
Same question for Paul.
Frank Slootweg wrote:downloads, normally multiple versions(e.g. 24H2) of different editions released at different points in time.
Andy Burns <usenet@andyburns.uk> wrote:
Daniel70 wrote:
When I brought this Desktop, it already had Win-11 installed .... so I >>>> don't have an .iso file.
Can I create an .iso file from what I've got ... or am I out of luck??
You can download .ISOs or make USB sticks using the Media Creation Tool. >>>
<https://www.microsoft.com/en-gb/software-download/windows11>
But the OP ('Jack') says this well known download capability is going >> away by October 14 (also for Windows 10). Is he just talking FUD?
Same question for Paul.
Win11
- once 25H2 is released to the public, the MCT and ISO links on the Win Msft Software Download web site are updated to the server hosting 25H2.
The only sites to obtain 24H2 become 3rd party links to their hosted download iso or MSFT server(when still available) or the volume licensing routes(Enterprise - M365 Admin site) or the subscription based Visual Studio portable(for available
Win10
- once 22H2 reaches EOL, there may or may not be a grace period prior to removal.
Not much different than in the past. The base software download web site for each os (Win11, Win10, Win8.1 Win7) will provide the best indication of availabilty for the respective os.
e.g. click on Windows 8.1 - yields a page with no download, but EOL information. While atm, the Win11 and Win10(since neither at EOL) once clicked redirect to the o/s download site for each.
- likewise M365 Admin and Visual Studio continue to host downloads(but only for a period of time).
You can make an ISO, or have Macrium burn a CD.
The output is about 300MB or so, and it will fit on a CD.
Only the inclusion of a large number of custom drivers, would tend to
break it for usage on a CD. The default drivers are quite frequently
good enough.
On Thu, 9/18/2025 10:49 AM, Frank Slootweg wrote:
Andy Burns <usenet@andyburns.uk> wrote:
Daniel70 wrote:
When I brought this Desktop, it already had Win-11 installed .... so I >>> don't have an .iso file.
Can I create an .iso file from what I've got ... or am I out of luck??
You can download .ISOs or make USB sticks using the Media Creation Tool. >>
<https://www.microsoft.com/en-gb/software-download/windows11>
But the OP ('Jack') says this well known download capability is going away by October 14 (also for Windows 10). Is he just talking FUD?
Same question for Paul.
There is no particular reason, for ISO media to be available past
the support interval for the OS.
When you enroll for the W10 ESU, that
is officially past the end of support.
If there was any SKU for which support lasted longer than Oct2025,
then the media should continue to be offered.
Win10 22H2 ISO has been on offer since, well, 2022, and it is 2025,
and you've had three years to get one :-)
The Win11 series is not in any danger, as 24H2 is available today,
and soon, the offered download will change to 25H2.
If you do go the image route, it helps to keep user-created data on a >different partition (or drive) - simply to keep the size of the image
file down. (you should still back up your data too of course, but that >doesn't _need_ an image - any sort of backup will work, even just
copying. I use FreeFileSync, that way I don't need to copy what hasn't >changed [though I should, occasionally].)
Paul <nospam@needed.invalid> wrote:
[...]
[About making Macrium Reflect 'Rescue media':]
You can make an ISO, or have Macrium burn a CD.
The output is about 300MB or so, and it will fit on a CD.
Only the inclusion of a large number of custom drivers, would tend to
break it for usage on a CD. The default drivers are quite frequently
good enough.
Well, I don't think I did anything special, but my (Windows RE 11
Build 22000 (64-bit)) Rescue media for Macrium Reflect Free (64-bit) v8.0.6867 on my Windows 11 system, was 717.9 MB, so it would probably
*not* fit on a normal CD. (I used a (8 GB) USB memory-stick, so size
was not an issue.)
[...]
On 2025/9/18 20:19:36, Char Jackson wrote:
Do you do anything to address the possibility of bit rot?
Not as much as I should.
I think rather than getting into complicated monitoring against rot,
just starting a complete new backup occasionally - though it may take
longer - is simpler.
On Fri, 19 Sep 2025 06:32:53 +0100, "J. P. Gilliver" <G6JPG@255soft.uk> wrote:
On 2025/9/18 20:19:36, Char Jackson wrote:<snip>
Do you do anything to address the possibility of bit rot?
Not as much as I should.
I think rather than getting into complicated monitoring against rot,
just starting a complete new backup occasionally - though it may take
longer - is simpler.
Sounds like the assumption is that the source files are always good and
only the backups are at any risk of damage. To a large degree, I follow
that logic here, but it may not be the perfect approach. I've seen cases here, where a damaged file is backed up and I'm not aware until much
later.
On Fri, 9/19/2025 3:12 AM, Char Jackson wrote:
On Fri, 19 Sep 2025 06:32:53 +0100, "J. P. Gilliver"
<G6JPG@255soft.uk> wrote:
Yesterdays experiment, was to upgrade a Windows 11 Pro 23H2 to 24H2.
Since 25H2 is incoming, the settings level in WU should be
"aggressive"
for 23H2 to 24H2, and it took giving the disk a rest for eight hours,
before WU admitted it was doing 24H2 (without my permission, just...
doing it). No, I'm pretty careful about these things, and I didn't
click
anything.
Paul
On 2025/9/19 14:37:22, Paul wrote:[...]
I had bad RAM on the WinXP machine, and out of idleness I would
sometimes run the Verify on the .mrimgs I was making on there.
And to my shock and horror, one of them had a bad verify (making
a little project for myself). I had to drop what I was doing,
and Verify in earnest.
Ah, I usually _do_ set the verify flag for my images, since they're
small so it doesn't take that long.
But - other than that I alternate
between two sets - I don't have anything similar for my data backups,
which are arguably _more_ important. (Though I do backup the Thunderbird
and Genealogy sections more often and differently.)>
But part of the problem with Windows and this sort of verification,
is the OS is always "doing things", so a lot of your work has to be
done offline, and even Macrium may leave a marker after a run,
so you hardly have forensic control of what is going on.
I always both make, and restore from, my images having cold booted from
the Macrium disc. (Actually I can't remember when I last had to do a restore.) I know Macrium _can_ make an image from a running system, I
just feel more secure not doing so.>
Paul wrote:
On Fri, 9/19/2025 3:12 AM, Char Jackson wrote:
On Fri, 19 Sep 2025 06:32:53 +0100, "J. P. Gilliver"
<G6JPG@255soft.uk> wrote:
Yesterdays experiment, was to upgrade a Windows 11 Pro 23H2 to 24H2.
Since 25H2 is incoming, the settings level in WU should be
"aggressive"
for 23H2 to 24H2, and it took giving the disk a rest for eight hours,
before WU admitted it was doing 24H2 (without my permission, just...
doing it). No, I'm pretty careful about these things, and I didn't
click
anything.
Paul
Did you have the computer paused? I brought up one other time that
Microsoft was going to ignore us.
On Fri, 9/19/2025 3:12 AM, Char Jackson wrote:
On Fri, 19 Sep 2025 06:32:53 +0100, "J. P. Gilliver" <G6JPG@255soft.uk>
wrote:
On 2025/9/18 20:19:36, Char Jackson wrote:<snip>
Do you do anything to address the possibility of bit rot?
Not as much as I should.
I think rather than getting into complicated monitoring against rot,
just starting a complete new backup occasionally - though it may take
longer - is simpler.
Sounds like the assumption is that the source files are always good and
only the backups are at any risk of damage. To a large degree, I follow
that logic here, but it may not be the perfect approach. I've seen cases
here, where a damaged file is backed up and I'm not aware until much
later.
I had bad RAM on the WinXP machine, and out of idleness I would
sometimes run the Verify on the .mrimgs I was making on there.
And to my shock and horror, one of them had a bad verify (making
a little project for myself). I had to drop what I was doing,
and Verify in earnest.
It turned out several of them were bad, did not pass Verify, and it
was bad RAM in some filesystem sensitive location doing it. I changed
out all four RAM sticks (as I could not MEMTEST and isolate to any
stick less than the entire set of four installed), and finally I
could make a .mrimg that would pass Verify. The WinXP machine had
DDR2 RAM, and by the time the machine died, I was on my third set
of RAM. The later machines don't do this. DDR4/DDR5, you can get
decent RAM now (and hey, even decent memory controllers).
You could go to the trouble of doing a hashdeep or md5deep of the file
tree, and do a restore on a test disk, and do the hashdeep on there.
It has an option to compare a previously prepared manifest against
a second disk. And that would tell you whether the clusters were
coming back, but it might not catch every security setting for the
files.
But part of the problem with Windows and this sort of verification,
is the OS is always "doing things", so a lot of your work has to be
done offline, and even Macrium may leave a marker after a run,
so you hardly have forensic control of what is going on.
On Fri, 9/19/2025 1:07 PM, Bill Bradshaw wrote:
Paul wrote:
On Fri, 9/19/2025 3:12 AM, Char Jackson wrote:
On Fri, 19 Sep 2025 06:32:53 +0100, "J. P. Gilliver"
<G6JPG@255soft.uk> wrote:
Yesterdays experiment, was to upgrade a Windows 11 Pro 23H2 to 24H2.
Since 25H2 is incoming, the settings level in WU should be
"aggressive"
for 23H2 to 24H2, and it took giving the disk a rest for eight
hours, before WU admitted it was doing 24H2 (without my permission,
just... doing it). No, I'm pretty careful about these things, and I
didn't click
anything.
Paul
Did you have the computer paused? I brought up one other time that
Microsoft was going to ignore us.
I used InControl to prevent 24H2 from coming in.
InControl was set to 23H2 before that, then I changed
the release value to 24H2. And the Upgrade came in without
any further prompting.
Paul
On 20/09/2025 11:20 am, Char Jackson wrote:
<Snip>
I've never had bad RAM, but many years ago when 20GB hard drives were considered huge, I bought one that quietly corrupted every single file
that I moved over to it. It didn't happen right away. Like every clever corruption issue, it waited a month or two until I was comfortable with
the new drive and satisfied that it was working properly.
"but many years ago when 20GB hard drives were considered huge".
I can remember, back in the day, I had a 10MB HD ... to which I applied
'MS Double Space' (was that about MS-DOS 5 or 6 or something??) which
then gave me about 18MB - 20MB.
Woo Hoo!! ;-P
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 13 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 148:45:43 |
| Calls: | 177 |
| Files: | 21,502 |
| Messages: | 79,014 |
