{Guide - Windows} Creating a custom Windows 10 ISO {Yoga Book-driver injection}

[Sandman45654]

Don't be sorry for having a life
Thank you for caring.
Have a nice day and see you later...

What error are you getting for the boot.win drivers?

 

[Lookasso]

What error are you getting for the boot.win drivers?

It's not an error.
It's in ntlite at the very beginning of your procedure.
I load the win installation, then I go on drivers like you says, but there is no boot.wim drivers folder there.

 

[Sandman45654]

It's not an error.
It's in ntlite at the very beginning of your procedure.
I load the win installation, then I go on drivers like you says, but there is no boot.wim drivers folder there.

Have you downloaded and extracted this file? I downloaded and checked it, the file appears to have everything included.

 

[jamespmi]

Now I'm installing the drivers manually but, it's in most cases impossible.
For example the drivers for the chipset, they have no exe, so to update them I must manually find the right device in device manager.

Nope, there is no exe as it is an *.inf installer... right click the *.inf file of every driver directory and choose INSTALL

 

[tcarole]

QC Check

Sandman, I have run through the NTLite portion of your instructions twice, producing identically-sized .iso's of 4.4GB. (My Yoga Book is currently on the 1803 release.) I noticed the pre-built .iso in your instructions is only 3.3GB. Should I be concerned that my builds may be incorrect somehow? And is there a way to check the integrity of the .iso before installing it on the USB drive and committing it to my Yoga Book? If not, what would recommend to ensure I can back up to my current configuration is something goes wrong?

 

[Sandman45654]

Sandman, I have run through the NTLite portion of your instructions twice, producing identically-sized .iso's of 4.4GB. (My Yoga Book is currently on the 1803 release.) I noticed the pre-built .iso in your instructions is only 3.3GB. Should I be concerned that my builds may be incorrect somehow? And is there a way to check the integrity of the .iso before installing it on the USB drive and committing it to my Yoga Book? If not, what would recommend to ensure I can back up to my current configuration is something goes wrong?

The prebuilt ISO has been compressed using ESD compression. This actually does decrease the ISO by a tad over a gigabyte. It does increase the time it takes to install Windows by about 5 minutes. This was done as I have a 1.5 Mbps upstream.

NTLite by default verifies the WIM file which contains the actual setup files. I am pretty sure Windows setup verifies the files as well. I have done over 200 tested builds for a hand full computers and I have yet to have one installation error. I'm sorry but I didn't think ahead and save the ISO files hash. I no longer have the original.

 

[tcarole]

The prebuilt ISO has been compressed using ESD compression. This actually does decrease the ISO by a tad over a gigabyte. It does increase the time it takes to install Windows by about 5 minutes. This was done as I have a 1.5 Mbps upstream.

NTLite by default verifies the WIM file which contains the actual setup files. I am pretty sure Windows setup verifies the files as well. I have done over 200 tested builds for a hand full computers and I have yet to have one installation error. I'm sorry but I didn't think ahead and save the ISO files hash. I no longer have the original.

Thanks for the confidence-builder. You have done a hell of a job pulling this all together, and I trust your expertise far more than mine. As soon as I can pick up a USB thumb drive big enough for a recovery disk I will take a deep breath and let 'er rip. I'll let you know how it works out.

 

[Sandman45654]

Thanks for the confidence-builder. You have done a hell of a job pulling this all together, and I trust your expertise far more than mine. As soon as I can pick up a USB thumb drive big enough for a recovery disk I will take a deep breath and let 'er rip. I'll let you know how it works out.

Wow all I can say is thank you! So long as you use a quality flash drive and a computer to match you should have zero Integrity issues.

 

[dproldan]

I used your instructions and can confirm that they also work perfectly with Windows 10 LTSB 2016. Yoga is fast and stable, thank you for your time documenting this process!

Only issue I think I have is fast charging functionality is not working. I'm using the original AC adapter and cable, but when I use HWiNFO64 to see the charge rate, it stays at 0.5-0.8 W. So it takes several hours to charge even 10-15%of the battery. I'm trying to find if there's any special driver (cmbatt.sys maybe?) for this in the factory images. Have you seen any problem with fast charging?

 

[Sandman45654]

I used your instructions and can confirm that they also work perfectly with Windows 10 LTSB 2016. Yoga is fast and stable, thank you for your time documenting this process!

Only issue I think I have is fast charging functionality is not working. I'm using the original AC adapter and cable, but when I use HWiNFO64 to see the charge rate, it stays at 0.5-0.8 W. So it takes several hours to charge even 10-15%of the battery. I'm trying to find if there's any special driver (cmbatt.sys maybe?) for this in the factory images. Have you seen any problem with fast charging?

LTSB editions of Windows 10 are aimed for enterprise level servers. There is a very good chance that frivolous "laptop" features like quick charge have likely been removed. I haven't been able to find a definitive list of everything removed from these builds but I will continue to do a little more digging.

 

[Sandman45654]

Windows 10 LTSB UPDATE:

LTSB builds do appear to limit charging capabilities. After reading more about Window 10 LTSB builds I've decided to do a test build myself. My Yoga Book charges at an amazingly low rate of 0.35 amps!! This is with all the proper drivers installed. Because of this I do believe my guess is accurate in saying that this is something Microsoft intentionally removed. If I happen to find a way around it I will post it. Considering this version actually seems to run slower than stock Windows 10 I will probably not spend a lot of effort in doing so.

Charging with the laptop completely powered off should, in theory Quick Charge. I will test this later once my battery has drained some more.

 

[Fidiii]

Just used the custom ISO provided in OP to give my yogabook a fresh start after almost 18 months of win updates and dubious software uninstalls.

Everything ran smooth as waxed butter, thanks for this amazing work! It's good to feel like day one again =)

 

[jamespmi]

Considering this version actually seems to run slower than stock Windows 10

LTSB is intended for devices that do not need feature updates at all. For example for computers that stays in a certain place for years with just a few apps running on it. No updates or new features needed, without a daily use, only doing a few main or concrete tasks. Imagine ATM's, some used XP until now.

I think it would be way more interesting to test Windwos 10 Lean once it's out...

 

[Sandman45654]

LTSB is intended for devices that do not need feature updates at all. For example for computers that stays in a certain place for years with just a few apps running on it. No updates or new features needed, without a daily use, only doing a few main or concrete tasks. Imagine ATM's, some used XP until now.

I think it would be way more interesting to test Windwos 10 Lean once it's out...

I hadn't heard of Windows lean yet! I also did a stripped build of LTSB and even though it booted using 1 gig of RAM and only 65 services I could tell it had been altered for stability.

:Edit
That build had 499 components removed! Windows 10 Pro CB runs blazingly fast with the same components removed.

 

[azcharey_20]

Hello, sir @Sandman45654! Do you have the ISO in other online storage?

 

[Sandman45654]

Hello, sir @Sandman45654! Do you have the ISO in other online storage?

No, I apologize I do not. With a 1.5 mbps upstream I stick with what has proven stable for me.

 

[samozen]

hello

Hello.
thanks for your guide. i follow everything and update to last bios. but wen boot from USB in setup i cannot use the touchscreen neither the keyboard work. what should i do? please help me.

 

[Sandman45654]

Hello.
thanks for your guide. i follow everything and update to last bios. but wen boot from USB in setup i cannot use the touchscreen neither the keyboard work. what should i do? please help me.

There are only really two options here. One, the BIOS update didn't actually take for some reason. Two, the drivers weren't properly injected into the boot.wim file. The Halo keyboard will never work in the BIOS unless Asus releases a firmware updated to do so. The drivers simply aren't there.

 

[samozen]

There are only really two options here. One, the BIOS update didn't actually take for some reason. Two, the drivers weren't properly injected into the boot.wim file. The Halo keyboard will never work in the BIOS unless Asus releases a firmware updated to do so. The drivers simply aren't there.

i update bios to version 04wt22ww mein was 04wt18ww

 

[Sandman45654]

i update bios to version 04wt22ww mein was 04wt18ww

Are you positive the 2 drivers were injected into the boot.wim file?