Bug: Image Size

[francis11]

Sure - and old XP/ 7 specialist what most of us have forgotten
Maybe i should go back if it wasn't for the work demanding newer build, ie. Office.
But still thinking hospitals in England have a lot of XP machines be hacked even they supposed to be off grid!?!
On Searx you can ping every open machine avaible on internet - find the right adress and i'm sure neighbours cooler is shut down

 

[Clanger]

air-gapped is always safest. specialist in what i need to know for my stuff, not an all round tech wallah like many in here, im still "home user plus"

 

[francis11]

Then we're equals. although history cannot be erased, but it is all about interests.
So with all due respect.

 

[Hellbovine]

Bump to see if this has been received. Please know that I'm not trying to rush, I recognize it's the holidays and there's been a ton of activity on the forums in the last few months. I only want to make sure this didn't get forgotten is all, since it seems like a fairly major bug. The reason I'm checking up is because I'm about to renew my license and start making a bunch of images again, and want to know if this issue has additional consequences I need to be concerned about in those images, and how to mitigate it. Thank you.

 

[Kasual]

Garlin's explanation makes sense to me though, so I can understand if that's the problem. But what is curious, is how did nobody else notice this over the years too then? So that's why I kind of lean towards bug, but I'm not sure.

I did notice when I started working (update + cache clean up) with Windows 10 20H*, as it wasn't an issue with older versions, I didn't really care because I saw more changes to Windows from Ms.