New autounattend problem

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.

I have to use other programs since I have problems with NTLite.

What are theirs? Isn't that weird?
 
Last edited:
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.
 
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.

But I had the same problems with VirtualBox and I know that but I'm forced to use both.

Now NTLite and WinReducer convert the install.esd to install.wim. The image will grow bigger in NTLite's case and if I convert it back to ESD it will have the same size as the WIM and won't be smaller and if I use the other WinReducer program to convert to ESD it will have the same size as WinReducer's WIM and not smaller! Also, if I use one after the other (NTLite and WinReducer) the install says (in both Hyper-V and VirtualBox) that I don't have enough space which isn't true and because of that I can't install Windows!
 
Last edited:
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.
 
Last edited:
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.

Well, but like I said I have problems if I only use one of them but it looks like I also have if I use both. So, they recommend those 3rd party tools?
 
Last edited:
Not (nuhi's tools) what Clanger listed, Ms officially recommends at least backup and recovery tools, is what i have seen in their site.

Ok.

EDIT: It's taking hours to install Windows 10 in Hyper-V even after using only WinReducer (with NTLite's autounattend)!

EDIT 2: This problem happens even in an untouched ISO!

EDIT 3: Now it only works with NTLite and not WinReducer!
 
Last edited:
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
 
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

I did what you said (using only NTLite and VirtualBox) and I still had problems.

EDIT: Does anyone know how can I use the "Repair your computer" option after making an unattend file with NTLite since it skips the first screen which this option shows up?

Strange, I removed .NET Framework 3.5 and now I have .NET Extensibility 3.5, whatever that is.

I removed Windows Defender with NTLite and some of its components and services are still running and the MMC Extended View is broken!

Which app is responsible for the lock screen and how can I remove the removable drives in file explorer below the hard drives so that I don't have it replicated?
 
Last edited:
@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.
 
@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.

Sorry, but I didn't understand how can I use the "Repair your computer" option while keeping the autounattend.

But they are running after a clean install and not after using live removal! Anyway, how can I delete them that way?
 
Last edited:
Delete autounattend.xml and you will be able to use it.

So, there's no way I can keep that option and use the autounattend.xml? What if I use YUMI to multiboot the Windows 10 installer, Windows 10 PESE and the Windows 10 Recovery Disc? Will I have any problem? How can I make an ISO out of the recovery disc files?

EDIT: What is this "HEVC Video Extension" new app and how can I remove it with NTLite?

EDIT 2: NTLite ignores an Adobe Flash Player update when I try to integrate it in boot.wim (not in install.esd)! Another problem is that I removed with NTLite Adobe Flash Player for Internet Explorer (because I don't need it since I removed Internet Explorer) so did I do the right thing by integrating the mentioned update (I also have the ignore problem when integrating the Adobe Flash Player update if I don't remove Adobe Flash Player for Internet Explorer)? Should I not integrate the mentioned update, after all? After removing the Adobe Flash Player for Internet Explorer will I have any problems regarding Flash (like in other browsers)? The update integration was not successful after removing Adobe Flash Player for Internet Explorer so does that mean that this Adobe Flash Player is like a generic thing and not only for Internet Explorer? In that case I won't remove it in spite of removing Internet Explorer and will integrate the update. I tried not removing Adobe Flash Player for Internet Explorer and integrating the update and this time it was successfuly integrated although it still says during the process that it was ignored in boot.wim! Also, I apply the settings to install.wim and boot.wim but afterwards I remove the unneeded edition which is boot.wim so does that mean that I'm losing time doing things with boot.wim for nothing? If I keep boot.wim I won't recover some diskpace? Will I have any problems if I remove it? Why does boot.wim still show up after I load the extracted ISO files after removing it?
 
Last edited:
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..
 
@Kasual, "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."

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. :)
 
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 did read but I don't know what it has got to do with the subject. Then why does it say that is was ignored? Anyway, could you answer to my other questions regarding boot.wim?
 
Last edited:
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´m not sure about replacing the boot.wim but, i found once in the net (about 7-8 years), a tool to handle drives and/or the information on it, this not so legally and unpopular distributed tool but, sometimes i use it, was built to run from USB (at that time there were no easy tools to run WinPE from USB other than from CD/DVD). I still use that old tool to: backup, easy files/folders removals when 'unlocker' doesn't works, clon, repartition, password removals, add or remove accounts in windows installed, install win 7 or 10 from ISOs dropped into the USB flash drive (manual install component must be kept), having said this, i think you can replace the win7 boot.wim with the 10 boot.wim.

For now, i'm out of time to build and share processes to customize a winpe, but if you do a search in google, you could get usefull and really interesting info about winpe tools.

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?


About HEVC Video, no idea.

About having access to recovery, delete autounattend.xml (if you don't mark the check boxes to copy it to another location, is really easy).
 
@Windows 10 User, if an update was tried and ignored, it will state why. Most commonly "it does not apply to this image".
If you are sure it is for that image and wasn't integrated previously, please retry only it on a clean ISO and if still is ignored, send me an exact filename of it and the ISO description.

Thanks.
 
Back
Top