Autounattend problem (WinReducer)

Status
Not open for further replies.
W

Windows 10 User

Active Member
I can't create a local account after accepting EULA and hiding boot image selection, cortana setup and online account options. This happens after I used WinReducer EX-100. After I install Windows 10 it's asked an "other user" password and not the password from the user I created since that OOBE step was skipped.

Is it possible to copy NTLite's autounattend configuration (which doesn't have this problem) to WinReducer's? But if I do that I'll mess with WinReducer's autounattend which despite not being ok has one option that can't be configured in NTLite. Also, I'd like to skip the password hint OOBE step.

EDIT: I tried adding some paragraphs from WinReducer's autounattend to NTLite's and copy it to the ISO and it looks like it is ok although I maybe should've copy more paragraphs to have the right configuration and now I have a new "Something went wrong You can try again, or skip for now." error message showing up on the OOBE but I can still proceed, anyway. I still want to have NTLite's autounattend configuration and the important parts from WinReducer's.
 
Last edited:
Kasual said:
VirtualBox is useful for testing NTLited ISOs before installing in a real environment.

Where is the product key to be read?

useles apps is the "new" windows platform

Setup will read only one xml file, if it is named autounattend.xml.

NTLite removes the calculator app located in Windows Apps - Apps

Unified telemetry client (asimov) and CEIP SQM (customer experience improvement program)located at remote and privacy
Click to expand...

I'll see if I have a problem in the host after I didn't have one in VirtualBox.

Forget it, I was testing two different configurations.

And what about the presets? What would happen if it had two different presets from the same program or one from each of the two programs?

I know, but let me remove it with WinReducer.

What does that have to do with the telemetry option in the other tab?

EDIT: Now I have another problem after configuring the Components, Resources and Services tabs in NTLite. Hyper-V asks me to press a key and after I do that it restarts and enter an infinite loop.
 
Last edited:
Windows 10 User said:
What would happen if it had two different presets from the same program or one from each of the two programs?

What does that have to do with the telemetry option in the other section?

EDIT: Now I have another problem after configuring the Components, Resources and Services sections in NTLite! Hyper-V asks me to press a key and after I do that it restarts and enter an infinite loop!
Click to expand...

The preset will be used as far as it is recognized.
The telemetry in service is something that can't be removed, only deprecated.
Don't know.
I give up.
 
Kasual said:
The preset will be used as far as it is recognized.
The telemetry in service is something that can't be removed, only deprecated.
Don't know.
I give up.
Click to expand...

Well, it's WinReducer's fault for not removing those things that I suppose it should, at least according to NTLite. NTLite's asks me to convert the image and if I say no it does nothing and after saying yes the image growths in size (!) so I'll have to use NTLite first and WinReducer next.

What telemetry in service? It doesn't make sense not being able to remove it.

EDIT: After I boot up the ISO made by NTLite in Hyper-V an error message says that Windows cannot read the setting from the unattend answer file as soon as I press a key to begin the install. What should I do now since I want to have this file?

EDIT 2: Now I tried the autounattend.xml file in an untouched ISO and I didn't have this problem so it might be caused by something removed by NTLite.
 
Last edited:
In short and as far i understand:

It works with everything (files and folders) compressed in the drive, about the same as you can access and edit to a mounted image (you can access to zip files from windows explorer as you normally access to a folder), i have tested compact 15 years ago but in late years but it works normally as editing a mounted image, i don't think the boot process takes longer than normally does and if so, there is not much difference.

It doesn't save space in compressed files/installers.

In some files it would save from 15% up to 95% in text files, most saves 40% to 60%.
 
Kasual said:
In short and as far i understand:

It works with everything (files and folders) compressed in the drive, about the same as you can access and edit to a mounted image (you can access to zip files from windows explorer as you normally access to a folder), i have tested compact 15 years ago but in late years but it works normally as editing a mounted image, i don't think the boot process takes longer than normally does and if so, there is not much difference.

It doesn't save space in compressed files/installers.

In some files it would save from 15% up to 95% in text files, most saves 40% to 60%.
Click to expand...

Will the install take more time and will it save some disk space? Will it break something, like Windows 10 PESE?
 
Last edited:
Here is the description:
Specifies that Windows should be installed with compression enabled. This might cause the installation process to take longer. If you are using a previous version of Windows PE, the Windows overlay filter driver (wofadk.sys) from the Windows 10 ADK must be included in the Windows PE image.

I have no idea about PESE nor what that means.
 
Kasual said:
Here is the description:
Specifies that Windows should be installed with compression enabled. This might cause the installation process to take longer. If you are using a previous version of Windows PE, the Windows overlay filter driver (wofadk.sys) from the Windows 10 ADK must be included in the Windows PE image.

I have no idea about PESE nor what that means.
Click to expand...

PESE is a custom-made Windows PE.
 
Last edited:
Status
Not open for further replies.
Back
Top