Windows could not set the offline locale information.

[zsae3452sfhkd]

Hello everyone,

This is my first time using this program. I downloaded a win 10 en-US iso from microsoft's official site, loaded the home single language edition into NTLite, removed ~50 components, trimmed out the remaining editions and created a bootable USB using rufus.

However, while installing windows I get the "offline locale information" error. I did some research on past posts in the forum, but did not find any conclusive answers. I have attached the XML and log files i found in the created iso.

If it matters, I ran into multiple "The system cannot find the file specified" errors while removing components. Also, rufus reported a "revoked uefi bootloader" message while trying to create the usb, but i just ignored it.

Any guidance on this issue will be appreciated. Thanks.

 

[nuhi]

Hello,

tested it and no issues.
Are you sure nothing else was used, like external unattended settings? As that error message sounds like a badly set language in the autounattend.xml file.

You can try Unattended in NTLite instead - it was not enabled in the attached preset, maybe it was in a previous session.
Potentially Rufus Windows options for the image, just throwing ideas how to isolate the cause.

 

[zsae3452sfhkd]

Hello,

tested it and no issues.
Are you sure nothing else was used, like external unattended settings? As that error message sounds like a badly set language in the autounattend.xml file.

You can try Unattended in NTLite instead - it was not enabled in the attached preset, maybe it was in a previous session.
Potentially Rufus Windows options for the image, just throwing ideas how to isolate the cause.

Thank you for your response. I'm sure no external unattended settings were used. Prior to the session in which I created the iso, i had loaded the vanilla iso in NTlite to just go through the program's capabilities firsthand. Then i uninstalled NTlite, installed the latest version and created the modified iso.

Attached are Rufus settings that were used. One difference i noticed is that the default file system in case of the vanilla iso is NTFS, while it is fat32 for the NTlite iso.

Since you confirmed that the component removals don't lead to an issue for you, I will first install windows 10 using the vanilla iso, and then retry creating the NTlite iso. I'm currently on windows 11 and i did make some changes with system files in the past.

If it still doesn't work, I'll try to use NTlite unattended as per your advice. I have never used an unattended setup in the past since I never needed it, hence I'll use it as a last resort.

Thank you again for your time, I will do the above steps and let you know about the results

 

[zsae3452sfhkd]

Hello,

tested it and no issues.
Are you sure nothing else was used, like external unattended settings? As that error message sounds like a badly set language in the autounattend.xml file.

You can try Unattended in NTLite instead - it was not enabled in the attached preset, maybe it was in a previous session.
Potentially Rufus Windows options for the image, just throwing ideas how to isolate the cause.

Retrying on a fresh windows 10 installation worked for me. I didn't get any "The system cannot find the file specified" errors while removing components this time. Also this time i created the iso without removing the other editions of windows.

Thank you and have a good day

 

[garlin]

Also, rufus reported a "revoked uefi bootloader" message while trying to create the usb, but i just ignored it.

Rufus now checks the boot loader file version on your ISO, as a public service. It doesn't know if you have already followed MS instructions on updating your UEFI BIOS or not, but will alert you if your ISO has the old version.

NTLite will allow you switch to the new boot loader, if the right updates have been applied to an image. If your version doesn't match what the UEFI expects, then the USB drive simply won't boot. Because it worked for you, I wouldn't worry about Rufus' warning for now.