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

[Sandman45654]

You will only need a KMS activator if you are trying to install Pro on a Home machine. Otherwise your Windows install will automatically activate.

 

[[[ Cold ]]]

Do you have a txt of what you removed in your personal build ? I'm tempted to try a really lite windows version but have no clue what can / can't be removed

 

[Sandman45654]

Do you have a txt of what you removed in your personal build ? I'm tempted to try a really lite windows version but have no clue what can / can't be removed

This is taken straight from the NTLite preset I made to strip my builds. The top of the list is drivers. The bottom is actual Windows components. You will need the full version of the app to remove these components. NTLite cost roughly $50 but is well worth it if you want (almost) full control over Windows. NTLite is written and maintained by one person and yet his support is still top notch! I emailed the creator on Christmas eve, not expecting a reply until after the holidays I was surprised to receive a response within 2 hours!

 

[azcharey_20]

Hello, sir @Sandman45654! ?

I meticulously followed your instructions. I used the 1709 x64 Pro ISO downloaded via Media Creation Tool. During the setup phase, when it asked me to connect to a wifi, I connected to our network and it stated that it was going to look for updates.

Installation went well, but the pen LED just blinks. The keyboard works and its light brightness can be adjusted via Halo Keyboard app, but doesn't vibrate on keypress or make sounds even if enabled in the Halo Keyboard app.

Was this instruction made using Win10 1703? Is it okay to use 1709 for this instruction?

 

[Sandman45654]

This guide was originally written using 1703. Everything except haptic/tone feedback is working correct? The 3 main things that could cause this issue are 1. RegistryEntries.reg wasn't added. 2. The system32 folder wasn't properly merged into the Windows folder. 3. Mms.msi (multi-mode service) and hkb.msi (halo keyboard) wasn't installed properly.

To try and fix this you can install hkb.msi then mms.msi. After that merge (run) RegistryEntries.reg and copy the downloaded system32 into the installed Windows folder. Reboot and you should be all set.

There is always a chance that something in one of the updates is causing the issue. Over the next few days I will backup my Yoga book and test installing with updates.

 

[azcharey_20]

This guide was originally written using 1703. Everything except haptic/tone feedback is working correct? The 3 main things that could cause this issue are 1. RegistryEntries.reg wasn't added. 2. The system32 folder wasn't properly merged into the Windows folder. 3. Mms.msi (multi-mode service) and hkb.msi (halo keyboard) wasn't installed properly.

To try and fix this you can install hkb.msi then mms.msi. After that merge (run) RegistryEntries.reg and copy the downloaded system32 into the installed Windows folder. Reboot and you should be all set.

There is always a chance that something in one of the updates is causing the issue. Over the next few days I will backup my Yoga book and test installing with updates.

Sir, it worked! Thank you so much!

I'm going to try it again with 1709. I did not do this solution when I did this entire thing with 1709.

Thank you again, sir!

 

[Sandman45654]

Sir, it worked! Thank you so much!

Awesome I'm glad the fix wasn't to big of a hassle! Thank you for the feedback. I will go ahead and do test build/install when possible to check for any new issues.

 

[azcharey_20]

Hi, sir @Sandman45654.

So after resolving the issue, I did another test. I followed your guide again using 1709 and did a clean install. Installation went well, but this time, the pen LED isn't blinking anymore as if the driver wasn't installed. This time, it was functioning properly. Pressing it would switch in between keyboard and pen mode. Also, the keyboard sound was working this time. The only problem left is the vibra on keypress. I did the workaround you suggested, but it didn't resolve the issue.

After that, I used the custom 1703 ISO again to do another clean install. Installation went well. This time, no problem experienced. Halo Keyboard was installed properly, pen LED functions well, keyboard sound and vibra works. I didn't have to do the workaround you suggested upon finishing the installation.

 

[Sandman45654]

Hi, sir @Sandman45654.

So after resolving the issue, I did another test. I followed your guide again using 1709 and did a clean install. Installation went well, but this time, the pen LED isn't blinking anymore as if the driver wasn't installed. This time, it was functioning properly. Pressing it would switch in between keyboard and pen mode. Also, the keyboard sound was working this time. The only problem left is the vibra on keypress. I did the workaround you suggested, but it didn't resolve the issue.

After that, I used the custom 1703 ISO again to do another clean install. Installation went well. This time, no problem experienced. Halo Keyboard was installed properly, pen LED functions well, keyboard sound and vibra works. I didn't have to do the workaround you suggested upon finishing the installation.

First and foremost thank you again for all of your testing and feedback. If I recall correctly the any pen light will only flash if the multi-mode driver isn't installed correctly. Normally when in keyboard mode the light will remain off. In writing mode it should remain lit. I have once or twice had to go into the halo app and disable/enable vibration to make haptic feedback work. That was early in the process (long before sharing) of figuring all this out however. Something else that has control over that light is Lenovo's shutdown helper. During shutdown the any pen light will remain lit until the laptop is fully shutdown. The new shutdown procedure in Windows 10 looks like it's shutdown long before the system has actually powered down. If you've ever shutdown when you meant to restart and tried to power back up when the screen was dark you'll know what I mean.

How soon after Windows finishes installing do you reboot your Yoga Book? Is it before installing other programs/updates? I've always done so right after installation finishes. That could be one possibility.

I will do my best to do a test build of both 1703 and 1709 (with setup downloading updates) looking for any new issues tonight or the next.

I would also like to touch up the guide a little more to try and make things as clear as possible. I am open to any and all opinions on doing so. I can't decide if I should add pictures to the guide or add annotations to the video or something else.

 

[Sandman45654]

I have finished testing I have done three fresh builds. One using 1703 (WIM based), one with 1709 (WIM based), and the last one was 1709 downloaded using the Microsoft Media creation Tool (ESD based). Each build was installed a minimum of at least two times. Windows Setup was also connected to wifi/internet to allow updating each time. The only thing new I noticed is that after rebooting for the first time after Windows setup is complete is that there is a short hesitation (30-45 seconds roughly) before haptic feedback and the Any Pen button actually activate. On subsequent reboots the hesitation is gone. For some odd reason it seems to only affect builds done using ESD based ISO images. I want to do a little more testing with the ESD v. WIM based installs next chance I get to make sure it is the ESD ISO's and not the internet causing the hesitation. If ESD ISO's prove to be problematic I will remove the Microsoft Media creation Tool from the guide.

 

[azcharey_20]

I have finished testing I have done three fresh builds. One using 1703 (WIM based), one with 1709 (WIM based), and the last one was 1709 downloaded using the Microsoft Media creation Tool (ESD based). Each build was installed a minimum of at least two times. Windows Setup was also connected to wifi/internet to allow updating each time. The only thing new I noticed is that after rebooting for the first time after Windows setup is complete is that there is a short hesitation (30-45 seconds roughly) before haptic feedback and the Any Pen button actually activate. On subsequent reboots the hesitation is gone. For some odd reason it seems to only affect builds done using ESD based ISO images. I want to do a little more testing with the ESD v. WIM based installs next chance I get to make sure it is the ESD ISO's and not the internet causing the hesitation. If ESD ISO's prove to be problematic I will remove the Microsoft Media creation Tool from the guide.

Oh wow! Haptic worked on 1709?! That's awesome, sir @Sandman45654!

Sir, how do I acquire the WIM based 1709, and is it also applicable to the tutorial that you created? I am currently downloading an ISO with a filename "en_windows_10_multi-edition_version_1709_updated_dec_2017_x64_dvd_100406711". Is there a way to identify if it's a WIM based 1709? Info about the file states that it came from "VLSC/MSDN"...

 

[Sandman45654]

Oh wow! Haptic worked on 1709?! That's awesome, sir @Sandman45654!

Sir, how do I acquire the WIM based 1709, and is it also applicable to the tutorial that you created? I am currently downloading an ISO with a filename "en_windows_10_multi-edition_version_1709_updated_dec_2017_x64_dvd_100406711". Is there a way to identify if it's a WIM based 1709? Info about the file states that it came from "VLSC/MSDN"...

Yes Sir, haptic feedback worked with the 1709 ESD ISO! There was a delay after the first reboot before it began working. I did have one build that failed with haptic feedback but that was my fault as I forgot to merge the system32 folder. I mounted the WIM file to check for the touchsense files which were missing. After rebuilding the ISO the issue was resolved.

Windows ISO Downloader (listed on first post) will allow you to download WIM based ISO's straight from Microsoft's servers. This is the recommended method. Multi editions have been modded. I haven't tried using a multi ISO but I could easily see it failing. The main reason Microsoft's Media Creation Tool is listed is for those that don't trust alternative means of getting the ISO file. Like I've mentioned Windows ISO Downloader does download from MS servers but the app itself isn't a Microsoft product.

The quick and dirty way is just by the ISO's file size. Generally under 4gigs will be a ESD based install. Over 4gigs and it should be WIM based. This may not apply to a multi version ISO. The proper way of checking would be to mount the ISO (or open it in Winrar) and check inside the sources folder. There will be either install.wim or Install.esd. It is the largest file in the ISO so it is easier to find if you sort files by size.

 

[azcharey_20]

Just a heads up, everyone.

On all of my previous tests, I used ESD-based ISO's, those that I acquired through Media Creation Tool. At the moment, I am doing this tutorial with the use of 1709 that I downloaded via Windows ISO Downloader. As mentioned above, it's WIM-based. I hope everything goes well. I will update you all once I'm done.

 

[azcharey_20]

Hello again, everyone!

I just finished installing the custom 1709 installer on my Yoga Book. Again, the custom installer was created using Sir @Sandman45654's guide, but I used a different WIM-based ISO. It's the one with the filename "en_windows_10_multi-edition_version_1709_updated_dec_2017_x64_dvd_1004 06711" that I got somewhere. I experienced the Working-Halo Keyboard-No-Multi-Mode-No-Vibra issue again which I also experienced in the past, but I did the workaround Sir @Sandman45654 suggested here. Everything is working now.

 

[TKFT44]

I followed this guide very specifically and everything is fine except for the haptic feedback not working. For that, I followed the fix on page 7 that was reported to work, and I still have no haptic feedback. The registry entries, the MSI files, and the system32 folder were all done correctly from the beginning, and I have tried the fix multiple times, but still nothing. Anybody have any other ideas?

Thanks ahead for your time

 

[Sandman45654]

I followed this guide very specifically and everything is fine except for the haptic feedback not working. For that, I followed the fix on page 7 that was reported to work, and I still have no haptic feedback. The registry entries, the MSI files, and the system32 folder were all done correctly from the beginning, and I have tried the fix multiple times, but still nothing. Anybody have any other ideas?

Thanks ahead for your time

Thank you for your interest in this guide! Hopefully we can get things set straight on this issue. On Step 15, when dealing with the MSI files have you dragged the entire MSI folder into NTLite? If so this may be yours and azcharey_20's issue. This is the main thing I believe I need to clarify in the guide. With the MSI folder you must go into the folder and drag and drop each individual file into NTLite. Each file in the MSI folder starts with a single digit. This is the place on where the file should be on NTLite's list. The order of these files are essential. They are installed in order according to how they are added and using the wrong order will cause issues. Hope this help out

 

[TKFT44]

Thanks for getting back to me so quickly!

That part, I made sure to do correctly, in order. I think where things went wrong was copying the system32 folder. I ended up with the TouchSense files in C:\System32 instead of C:\Windows\System32 after the install. I have now corrected that mistake.

I was able to use the instructions in this thread ( https://forum.xda-developers.com/yoga-book/how-to/drivers-clean-windows-install-t3521403/page3 ) to get haptic feedback working again just now! I did have to make sure that vcruntime140.dll was in my System32 folder in addition to the supplied files, or the TouchSense service wouldn't start.

Thanks again for your help and all the time you've put into this guide!

 

[Sandman45654]

Thanks for getting back to me so quickly!

That part, I made sure to do correctly, in order. I think where things went wrong was copying the system32 folder. I ended up with the TouchSense files in C:\System32 instead of C:\Windows\System32 after the install. I have now corrected that mistake.

I was able to use the instructions in this thread ( https://forum.xda-developers.com/yoga-book/how-to/drivers-clean-windows-install-t3521403/page3 ) to get haptic feedback working again just now! I did have to make sure that vcruntime140.dll was in my System32 folder in addition to the supplied files, or the TouchSense service wouldn't start.

Thanks again for your help and all the time you've put into this guide!

You called it correct my friend! The directory layout should be C:\Windows\System32\TouchSense. With it placed in the correct folder you shouldn't need vcruntime140.dll. I will keep this file in mind in case more haptic feedback issues arise.

You are very welcome I have learned quite a bit along the journey. I do continue work on this project in my spare time. I have a couple more things I would like to add/change sometime down the road.

 

[TKFT44]

Well, what happened on my system was, I had copied the files to correct System32, but the command (from the other thread) to start the TouchSense service just hung and didn't respond, same with trying to start it from the Services menu.

When I navigated to System32 and double-clicked touchesensed.exe, I could then see the error in the command prompt that popped up. In my case, vcruntime140.dll could not be found. Putting that back in the System32 folder had everything working after a reboot.

I should say, vcruntime140.dll WAS there originally, but I had accidentally moved it during my testing.

 

[Sandman45654]

Well, what happened on my system was, I had copied the files to correct System32, but the command (from the other thread) to start the TouchSense service just hung and didn't respond, same with trying to start it from the Services menu.

When I navigated to System32 and double-clicked touchesensed.exe, I could then see the error in the command prompt that popped up. In my case, vcruntime140.dll could not be found. Putting that back in the System32 folder had everything working after a reboot.

I should say, vcruntime140.dll WAS there originally, but I had accidentally moved it during my testing.

Thanks for the feedback, much appreciated. I'm off now to do more work on my custom build!