Windows 10 User
Active Member
I do a combination of image removal and live install removal, you just need time, the werewithal, tea and nicotine. Insomnia also helps
Well, I've been doing this trial and error for months.
I do a combination of image removal and live install removal, you just need time, the werewithal, tea and nicotine. Insomnia also helps
Well, I've been doing this trial and error for months.
You have been using other tools, not NTLite only and that is why you have too many problems.
Ms officially recommends third party tools instead of some of theirs.
You should use VMWare or VirtualBox, not their Hyper-V.
They (Ms) recommends to use third party backup and recovery tools instead of their backup and recovery tools.
If you have problems with NTLite you should troubleshoot and report it back without using any other tool or not removing the needed component, but you tried to use it with every other tools and you will never success that way.
Take notes and read some more.
Yep it does take time. W10 isnt as tolerant as w7 with removals. Frankly, in all respects Windows 10 is a bastard, thats why i am having a break.Well, I've been doing this trial and error for months.
Yep it does take time. W10 isnt as tolerant as w7 with removals. Frankly, in all respects Windows 10 is a bastard, thats why i am having a break.
As Kasual says, stick with one tool only. Its easier for you to bughunt(game over man) and easier for Nuhi too.
Nuhi recommended VirtualBox(i think) and its ok, i dont use it much as i do direct to hardware test installs.
Your best friend when testing is a pen/pencil and paper for taking notes.
MS recommends 3rd party tools? nLite, vLite, NTLite. They missed(purposely ignored) a golden opportunity.
Not (nuhi's tools) what Clanger listed, Ms officially recommends at least backup and recovery tools, is what i have seen in their site.So, they recommend those 3rd party tools?
Not (nuhi's tools) what Clanger listed, Ms officially recommends at least backup and recovery tools, is what i have seen in their site.
Your grammer is hard to understand and people are trying their best to understand you to help you... You are not even doing what we tell you for help and after doing what you think you come here with even more problems. You are doing this in every thread you create and this way you will never create a bug-free os.. you will waste days weeks months to do that if you keep going in this attitude.... you have to stop using winreducer or hyperv AND post your problems simple way with your preset and simple explanation of problem. stop creating more problems before previous ones are solved. maybe then they can help you
@Windows 10 User , for repair options please see here.
If there are some Defender pieces running after a reboot, let me know which.
For those service entries, it's normal for Live removal as Windows does not allow to delete Defender pieces while it's running. You can delete them after reboot with regedit, they are under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
Careful about the other services, or leave as is.
Delete autounattend.xml and you will be able to use it.
Have you read the content in the link that nuhi gave you?
All i can say after reading the "tongue twister" paragraph is, boot.wim is not designed to be updated with windows updates as it is built for a specific purpose, besides it can be adapted for other purposes.
You are wrong when you state "NTLite ignores an Adobe Flash Player update when I try to integrate it in boot.wim", NTLite does not ignore updates, it tries to integrate every queued update..
I feel there is a Boot Wim topic here, because i would like to know more about the boot wim, what updates it has, if any, do we need to update or not annd what other purposes it can be adapted for. I have not done any work on the w10 boot wim but i did for my presets for windows 7. I shrunk the boot wim by removing PE and keeping only Setup, which i did update on occasion using the updates for the install wim then bareboning it while keeping it bootable for optical media and usb2 keys.
I have heard that you can install w7 by replacing its boot wim with the windows 10 boot wim, although i have never tried this i would like to know if it is possible, do you just replace the w7 boot wim with the w10 one? Do any flags or other things have to be changed in the boot wim to do this?
The only time most people mess with a boot wim is to install usb3 drivers(on w7) or remove PE so i think a Boot Wim topic would be a welcome addition to the forum.
I did read but I don't know what it has got to do with the subject. Then why does it say that is was igored? Anyway, could you answer to my other questions regarding boot.wim?