I've never actually used Macrium from within Windows, but would like to
keep it there. However, it includes two large files, which together come
to over a GB:
C:\boot\macrium\WinREFiles\media\sources\boot.wim C:\boot\macrium\WA10KFiles\media\sources\boot.wim
Are they needed? the folder being called "sources" makes me think not,
but ...
I've never actually used Macrium from within Windows, but would like to
keep it there. However, it includes two large files, which together come
to over a GB:
C:\boot\macrium\WinREFiles\media\sources\boot.wim C:\boot\macrium\WA10KFiles\media\sources\boot.wim
Are they needed? the folder being called "sources" makes me think not,
but ...
I've never actually used Macrium from within Windows, but would like to
keep it there. However, it includes two large files, which together come
to over a GB:
C:\boot\macrium\WinREFiles\media\sources\boot.wim C:\boot\macrium\WA10KFiles\media\sources\boot.wim
Are they needed? the folder being called "sources" makes me think not,
but ...
On 11/20/26 6:35 AM, J. P. Gilliver wrote:
I've never actually used Macrium from within Windows, but would like to
keep it there. However, it includes two large files, which together come
to over a GB:
C:\boot\macrium\WinREFiles\media\sources\boot.wim
C:\boot\macrium\WA10KFiles\media\sources\boot.wim
Are they needed? the folder being called "sources" makes me think not,
but ...
Iirc,
Those folders/files should be present if you created Macrium Rescue Boot media.
Providing the opportunity to boot a PC and restore a Macrium backup
image. Those folders/files i**do not** any of your personal files or previously created Macrium image backup.
If you've created Macrium Rescue Boot media and a Macrium backup image...best to leave the files.
If you've not created Rescue Media on the device, those two folders/
files may not/should not be present.
On 2026-11-20 17:24, ...w¤?ñ?¤ wrote:
On 11/20/26 6:35 AM, J. P. Gilliver wrote:
I've never actually used Macrium from within Windows, but would like to
keep it there. However, it includes two large files, which together come >>> to over a GB:
C:\boot\macrium\WinREFiles\media\sources\boot.wim
C:\boot\macrium\WA10KFiles\media\sources\boot.wim
Are they needed? the folder being called "sources" makes me think not,
but ...
Iirc,
Those folders/files should be present if you created Macrium Rescue
Boot media.
Providing the opportunity to boot a PC and restore a Macrium backup
image. Those folders/files i**do not** any of your personal files or
previously created Macrium image backup.
If you've created Macrium Rescue Boot media and a Macrium backup
image...best to leave the files.
If you've not created Rescue Media on the device, those two folders/
files may not/should not be present.
Just to be clear, these files are created when you first create *ANY*
rescue media, USB or Windows boot menu option.ÿ If they are deleted, if
you created a rescue Windows boot menu option, it will fail, and also
the next time you want to create any rescue media, they will have to be recreated, which will take longer and still require the original disk
space saved, hence my strong advice against deleting them.
I've never actually used Macrium from within Windows, but would like to
keep it there. However, it includes two large files, which together come
to over a GB:
C:\boot\macrium\WinREFiles\media\sources\boot.wim C:\boot\macrium\WA10KFiles\media\sources\boot.wim
Are they needed? the folder being called "sources" makes me think not,
but ...
If you are thinking of deleting them, I would advise strongly not.
On 21/11/2026 8:50 am, J. P. Gilliver wrote:
Given I have the boot media, I probably _could_ do without them, butWatch out for it being re-installed ... maybe after next Update Tuesday!
will take your advice and not: uninstalling Copilot (which I never use)
released more than twice the space!
On 2026/11/21 9:43:35, Daniel70 wrote:
On 21/11/2026 8:50 am, J. P. Gilliver wrote:
Given I have the boot media, I probably _could_ do without them, butWatch out for it being re-installed ... maybe after next Update Tuesday!
will take your advice and not: uninstalling Copilot (which I never use)
released more than twice the space!
Probably sooner than that; when I was trying to remove recent updates,
before I gave up and reloaded an earlier image (both of which turned out
not to have been necessary anyway), I invoked the "no updates for 7
days" thing. Assuming that request is stored remotely (so won't have
been erased by the rollback), I presume it'll come back sooner :-(.
On 21/11/2026 8:50 am, J. P. Gilliver wrote:
Given I have the boot media, I probably _could_ do without them, butWatch out for it being re-installed ... maybe after next Update Tuesday!
will take your advice and not: uninstalling Copilot (which I never use)
released more than twice the space!
J. P. Gilliver <G6JPG@255soft.uk> wrote:
On 2026/11/21 9:43:35, Daniel70 wrote:
On 21/11/2026 8:50 am, J. P. Gilliver wrote:Probably sooner than that; when I was trying to remove recent updates,
Given I have the boot media, I probably _could_ do without them, butWatch out for it being re-installed ... maybe after next Update Tuesday! >>>
will take your advice and not: uninstalling Copilot (which I never use) >>>> released more than twice the space!
before I gave up and reloaded an earlier image (both of which turned out
not to have been necessary anyway), I invoked the "no updates for 7
days" thing. Assuming that request is stored remotely (so won't have
been erased by the rollback), I presume it'll come back sooner :-(.
I'm quite sure the 'Pause updates' timer is set locally, not on some (Microsoft) server.
You can also extend the time (before it has expired) by switching off
your network, do a 'Check for updates' (which will fail because the
network is off) and then do another 'Pause updates'. It's unlikely that Microsoft is actually keeping track of all that fiddling. (I have used
this extension method on our extended (up to three months) trips.)
[...]
I didn't want to delay updates for the sake of it - it was just, when I
was thinking the most recent update might have caused my slowdown (it
seems highly likely it didn't - it seems it was a flaky battery [which
now seems to have recovered!] combined with an old battery-monitor
utility), I was just trying to make sure the update didn't immediately
get reinstalled when I uninstalled it.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 498678:21:48 |
| Calls: | 212 |
| Calls today: | 3 |
| Files: | 912 |
| D/L today: |
31 files (22,593K bytes) |
| Messages: | 69,867 |