[Noel]

mk2016 wrote:

Hi Noel. Thank you for sharing.
http://techtablets.com/forum/topic/installation-windows-10/#post-25549

I made a windows10 usb from iso (microsoft media creation tool).
When I check the contents of usb, I can find boot.wim and install.esd in sources directory instead of install.wim. What should I do? Sorry for my bad english.

Use this command to list the editions that are contained in the ESD:
dism /Get-WimInfo /ImageFile:D:\sources\install.esd

This should list Win10 and Win10 Pro. Take note of the index of the edition you want to extract. In this example I will extract index 1 which is Win10 Pro:
dism /Export-Image /SourceImageFile:D:\sources\install.esd /sourceindex:1 /DestinationImageFile:C:\install.wim /Compress:max

This will produce a WIM file which you can use with my previous directions.

[Noel]

I scrapped NTLite and used the Dism command line tool which comes with Windows to embed the drivers into install.wim and boot.wim. This time I embedded ALL of the drivers into boot.wim instead of just the touch drivers and this time I have a functioning touch screen in the installer. So I no longer need a hub/keyboard/mouse to get through the setup process.

I posted full directions here:
http://techtablets.com/forum/topic/installation-windows-10/#post-25549

BTW, Dism was able to embed the drivers WAY faster than NTLite did. Not sure why NTLite was so much slower.

[Noel]

I updated my instructions here:
http://techtablets.com/forum/topic/installation-windows-10/#post-25549

I have directions on how to export the original drivers and then embed these drivers into your install media so that you will have full functionality on first boot and even have a working touch screen in the windows installer.

[Noel]

Normally when you get those messages it’s due to a bad cable. It may be worth getting a new cable just to be safe. It would suck if the cable was damaged and ended up shorting out and killing the tablet.

When I plug mine in to charge I get a flashing LED and when it is done charging I get a solid LED.

[Noel]

Was it hard to open? I was curious what the internals are like. Is it just the 4 pentalobes?

[Noel]

Geez.. I just discovered a PowerShell command that would have made this whole process much easier.

Export-WindowsDriver –Online -Destination D:\drivers

I could have run that command before touching the tablet to export all non-Microsoft drivers to a USB stick in a folder named drivers.

BTW, I used NTLite to integrate all the drivers into install.wim and it worked perfect. Touch screen and everything works on first boot now. I also integrated the touch drivers into boot.wim thinking I could get the touch screen during the setup process but that didn’t work. My guess it the touch drivers rely on some other hardware (like USB drivers) or something like that. Next go around I will just integrate all the drivers into install.wim and boot.wim.

[Noel]

But I just tried this an don’t get any messages.

[Noel]

Are you saying you’re plugging the tablet into another computer to charge it? I haven’t tried this myself but I’m not surprised that you would get an error when connecting a USB host to another USB host. Typically you would connect a peripheral (printer, USB hub, USB thumb drive ect) to a host… not a host to a host.

[Noel]

I used Double Driver to back up all the non-Microsoft drivers on my Hi8 Pro. You can download them here:
https://www.dropbox.com/s/cnl9o3aiqosu3e9/Hi8ProDrivers.7z?dl=0

[Noel]

My tablet didn’t come with an OTG cable. It only came with a cable for charging. If you are talking about plugging the charge cable into a hub then that is your problem. That will not work. You need to get a USB-C hub or get an OTG adapter cable like the one in my link and then use your USB2 hub (USB-C is simply a connector. The tablet is USB3 but is backwards compatible with USB2).

[Noel]

I used Double Driver to back up all the installed drivers after my reload excluding any Microsoft drivers as those should be included in Win10. After zipping it is only 70MB or so.

 

I still have the full DriverStore incase something is missing from this archive.

 

Here is the link:
https://www.dropbox.com/s/cnl9o3aiqosu3e9/Hi8ProDrivers.7z?dl=0

[Noel]

I used this cable:
http://www.amazon.com/gp/product/B00XHOGEZG?psc=1&redirect=true&ref_=oh_aui_detailpage_o03_s00

And I’ve used a few keyboards without a problem.

I will package up the drivers tonight. I need to slim it down a little because the DriverStore I backed up has lots of drivers not actually needed for the Hi8Pro.

If can’t even get the keyboard to work in the bios then you have bigger problems. 🙁

[Noel]

Well it went smooth. Here is what I did.

First you need to create a USB installer with Microsoft’s media creator tool which you can download here:
http://go.microsoft.com/fwlink/?LinkId=691209

When it asks which version of Windows to download, make sure you select the 32bit version. The Hi8Pro only has a 32bit EFI so it can’t boot the 64bit installer. Once that is done, to make life easier (so you don’t have to type you cd key when installing) you can create a text file named PID.txt and put it on usb:\Sources with these contents:

[PID]
Value=YOUR-PRODUCT-KEY-HERE

Now, plug this USB stick into your Hi8Pro while booted into Windows and then right click on the start menu and then select “Command Prompt (Admin)” from the menu.

Now type these commands:

powershell
Export-WindowsDriver -Online -Dest C:\drivers

This will create a folder named c:\drivers on the USB stick and export all the custom drivers needed by the tablet.

Now let’s inject these drivers into install.wim and boot.wim so that your install media has all the drivers built in.

Assuming you didn’t close the command prompt, issue these commands:

mkdir C:\Win10boot
Dism /Mount-Image /ImageFile:D:\sources\boot.wim /Index:2 /MountDir:C:\Win10boot
Dism /Image:C:\Win10boot /Add-Driver /Driver:C:\drivers /Recurse
Dism /Unmount-Image /MountDir:C:\Win10boot /Commit

mkdir C:\Win10install
Dism /Mount-Image /ImageFile:D:\sources\install.wim /Index:1 /MountDir:C:\Win10install
Dism /Image:C:\Win10install /Add-Driver /Driver:C:\drivers /Recurse
Dism /Unmount-Image /MountDir:C:\Win10install /Commit

Now you have a USB installer that has all the drivers embedded in it.

Now for the install.

The easiest way to boot off this USB stick is to click the settings button from within Windows and then select “Update & security”. Then select Recovery. Then click the Restart now button under Advanced startup. It should then reboot and come to a screen with an option to boot of USB removable media. When you select that it will boot the USB stick and go through the standard Win10 install process. Because you embeded all the drivers into boot.wim you should have a working touch screen even within the setup program so you should be able to go through the whole process without needed a dedicated keyboard and mouse. When it’s time to select the partition to install to, simply remove all the existing partitions and let it create new ones.

Once your computer is booted you should have all the drivers preinstalled and be ready to go.

If you can’t get it to boot off the USB stick then another option is to boot into the bios and on the Save Exit screen you can select an override boot device. To boot to the bios simply hold the power button until the device turns off. Then press and hold the power and vol up buttons until you see the bios screen. If it still will not boot your USB stick then my guess is you built a 64bit installer.

If your tablet isn’t bootable and you have no way to extract the origional drivers, you can download the drivers here: https://www.dropbox.com/s/cnl9o3aiqosu3e9/Hi8ProDrivers.7z?dl=0 You can follow the directions for embedding the drivers from any Windows 10 machine. Just update the paths in my directions to match your environment.

[Noel]

I tried a USB stick that I created with the mediacreator tool but it didn’t work. Turns out its because the EFI on this tablet only looks for the x86 version of Win10. So I recreated my USB stick as x86 and it booted perfect. I didn’t follow through with the install yet. Also, before reloading be sure to snag a copy of the drivers which are found here:

“C:\Windows\System32\DriverStore\FileRepository”

 

I am going to reload this thing tomorrow and will report back how it goes.

[Author]

Posts