Bugs with direct deployed image editing [VHD direct editing]

had problem with removing
edgechromium 'Microsoft Edge (Chromium
doesnt takes effect, the comp appear after saving the image
 
with 7742 loading vhd
is getting stuck for a min in 58% in reading data
error 32 appear when loading preset

it doesnt fail to remove comps but take longer then wim
10k files takes 1.5 mins
 
Last edited:
Thanks guys, will setup that and report/fix tomorrow.

edit: Had no time for this today, got stuck on a previous task.
Thanks for your patience, hopefully tomorrow.
 
Last edited:
Managed to replicate, sending you a pre-release for fixed deployed image (VHD) loading registry issue, and Edge removal.

Let me know how it goes.
Thanks.
 
nuhi said:
pre-release
Click to expand...
tested on
en_windows_10_consumer_editions_version_2004_updated_dec_2020_x86_dvd_6b8faa36
'Microsoft Edge Chromium not been removed
the stucking in 58% not been resolved
btw i check taskmgr and other apps. doesn't seems to do something in the background

the error 32 - resolved
the time of removal took 3x faster - resolved
 

Attachments

  • Auto-saved session 388808c7.zip
    4.8 KB
Thanks, will get that exact ISO to test the remaining issues.
Reporting back tomorrow, late here now.
 
Got the exact ISO, it does not have Edge Chromium in it, for that it would need to be 2009, not 2004.
The reason why Edge Chromium is listed is as a placeholder, if you add it via an update 2004->2009, then you can remove it in one go.
It's also tagged as "Placeholder".

Haven't noticed any stucking at 58% reading data on my side, I see in your log you have it for a full minute.
Good news is that I see from the log what the task is, not that it makes sense but I'll try to optimize.
Same link, let me know how it goes.

Thanks.
 
Make sure not to use ramdisk as a temporary drive, where images will be mounted, only for Scratch disk, if it has enough room, maybe it's hitting the limit.

Btw deployed image registry load fix is now public.
Let me know if you find any other issues, especially with the newly introduced offline VHD/deployed method.

Thanks.
 
1614191808365.png
edge not been removed from winsxs
speech
windows 10 pro 20h1 64bit build 630

i guess maybe the iso is not original so the files removed from the system32 but not from winsxs
 

Attachments

  • 1614191959873.png
    1614191959873.png
    16.3 KB
1614791571303.png
i tested on windows 10 pro 64bit 2009 build 630
the edge and speech appeared in the removing process and also defender

it doesnt remove from winsxs

but the good news i cant find any more bugs with removing from vhd
i checked 3 diff isoes all ok
good job nuhi
 
Last edited:
ntlite doesnt remove recovery.wim from vhd
locate at L:\Recovery\WindowsRE
 
Last edited:
few bugs i found lately
auto saved presets are not always been saved
Compatibility changes doesnt get applied when using to remove all the branch at once
 
aviv00 said:
View attachment 4539
i tested on windows 10 pro 64bit 2009 build 630
the edge and speech appeared in the removing process and also defender

it doesnt remove from winsxs

but the good news i cant find any more bugs with removing from vhd
i checked 3 diff isoes all ok
good job nuhi
Click to expand...
Hi,

the WinSxS is cleaned very mildly unless Servicing Stack compatibility is turned off in Components - toolbar - Compatibility.
Without that compatibility it does not preserve updateability and no need for WinSxS leftovers, but you can update via Host Refresh.
 
aviv00 said:
few bugs i found lately
auto saved presets are not always been saved
Click to expand...
This was a temporary bug in 7816, should not be there in 7817+, let me know.

aviv00 said:
Compatibility changes doesnt get applied when using to remove all the branch at once
Click to expand...
I'm very interested in replicating this, can you please be more specific, what sequence will show this?

Thanks.
 
nuhi said:
Thanks, is the correct path:
\Recovery\WindowsRE\winRE.wim
or you indeed have "recovery.wim", literally?
Click to expand...
its as u said
i was wrong about the wim name

nuhi said:
7817
Click to expand...

u mean 7917+ right?
i was in 14 will update and try again
edit after updating ntlite:
its overwrite the last one with the new one

nuhi said:
I'm very interested in replicating this, can you please be more specific, what sequence will show this?
Click to expand...

It's looks like a mistake.

I locked down battery in "Hardware Support" via touch device
when i unmark the branch of "Hardware Support"
it open selection window with the title named "battery..."
so i looked up its inf files, its just "Drivers" category under name "Batteries" and even saying it will remove it
it did not eventually :)
 
Last edited:
You must log in or register to reply here.
Back
Top