Windows 10 RE (& Macrium PE) driver issues Asus X205TA

SD_83

New Member
Local time
7:19 AM
Posts
4
Thread starter
On Asus X205TA, there is issue with Touchpad on Windows 10, that wasn’t the case with Windows 8 as it had come pre- loaded with. Later Asus release Smart Gesture driver that fixed the problem in booted Windows, but not for Win RE or PE environment – neither keyboard nor touchpad worked in RE or PE environment. This is an UEFI system with GPT disk. Whereas, my other system Lenovo G570 (Legacy BIOS, MBR) had no issues in Win RE/PE environment whatsoever with any drivers.

The problem is particularly ominous while using Macrium PE for restoring images on Asus X205TA as neither Keyboard nor touchpad works. I am not sure if Asus is the problem or Windows 10 or Macrium Reflect; but any insight on this would be greatly appreciated. Asus X205TA has latest BIOS (Ver. 213), and all latest drivers installed.

Interestingly, if advanced options is entered through Shift+Restart, the RE picks up both keyboard and touchpad support from OS; BUT on a fresh start directly to advanced options it never gets the keyboard or touchpad support and results in no input device in RE. This is essential because if Windows become unbootable, then Macrium Image Restoration is the only way out to fix this problem quickly, and that is the whole point of using Macrium Reflect actually. I have tried picking up drivers individually during Macrium Reflect boot menu creation but to no avail. Even manually extracted inf dll & sys files to C:\boot\Macrium\WinRE Drivers – which didn’t help either.

Both systems run on Windows 10 19H2 (build 18363.997). Native base Win RE version was used in both cases to build the Macrium boot menu.

Thanks for any solution/leads.
 
Windows Version
Windows 10 19H2

My Computer

System One

  • Operating System
    Windows 10

johngalt

Well-known member
WQ Insider
Member
VIP
Local time
9:49 PM
Posts
785
Location
3rd Rock
Saw your post at BC also - a suggestion there already by the mod, let us know if that helps or not.
 

My Computer

System One

  • Operating System
    Windows 10 Pro X64
    Computer type
    PC/Desktop
    Manufacturer/Model
    The Beast Model A (homebrew)
    CPU
    AMD Ryzen 9 3950X
    Motherboard
    MSI MEG X570 GODLIKE
    Memory
    4 * Corsair Vengeance 32 GB 3600 MHz
    Graphics Card(s)
    eVGA GeForce GTX 970 SSC ACX 2.0 (04G-P4-3979-KB)
    Sound Card
    Realtek® ALC1220 Codec
    Monitor(s) Displays
    2 * Lenovo LT2323pwA Widescreeen @ 1920*1080
    Hard Drives
    3x Sabrent Rocket PCIe Gen4 NVMe M.2 1 TB SSD (SB-ROCKET-NVMe4-1TB)
    SanDisk Ultra SDSSDHII-960G-G25 960 GB SATA III SSD
    2 * Seagate Barracuda 7200.12 ST31000528AS 1TB 7200 RPM --> RAID1
    PSU
    PC Power & Cooling’s Silencer Series 1050 Watt, 80 Plus Platinum
    Case
    Fractal Design Define 7 XL Dark ATX Full Tower Case
    Cooling
    NZXT KRAKEN Z73 73.11 CFM Liquid CPU Cooler + Air (3 * 140mm fans from case)
    Keyboard
    SteelSeries Apex Pro Wired Gaming Keyboard
    Mouse
    Logitech MX Master 3 Wireless Laser Mouse(shared)
    Internet Speed
    AT&T Lightspeed Gigabit duplex
    Browser
    Nightly|Chrome|Canary|Edge+ (Chromium) (in all 4 flavors)
    Antivirus
    Windows Defender + MB 4

Fabler2

Active Member
VIP
Local time
2:49 AM
Posts
133
Location
Wales, UK
Not really a solution but more of a workaround. On the problem PC create another rescue media using Windows RE this time.

Screenshot_3.png


A bit confused here as you say 'using Macrium PE for restoring images' but also say ' Native base Win RE version was used'.
 
Last edited:

My Computer

System One

  • Operating System
    Win 10 Home
    Computer type
    Laptop
    Manufacturer/Model
    ASUS VivoBook
    CPU
    AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
    Motherboard
    ASUSTeK COMPUTER INC. X509DA (FP5)
    Memory
    8 GB
    Graphics Card(s)
    RX Vega 10 Graphics
    Monitor(s) Displays
    Generic PnP Monitor (1920x1080@60Hz)
    Hard Drives
    476GB INTEL SSDPEKNW512G8
    Internet Speed
    25 Mbps
    Browser
    Edge
    Antivirus
    Defender

iko22

Active Member
Member
VIP
Local time
2:49 AM
Posts
170
Location
South West England
As a matter of interest, how are you adding drivers to the driver store? Had you tried using DISM to add or query the drivers in WinRE?
If you first mount the Windows image with
md C:\mount\windows
Dism /Mount-Image /ImageFile:C:\mount\install.wim /Index:1 /MountDir:C:\mount\windows
where C:\mount\windows is the location of your offline Windows image.
Then mount the offline WinRE image with
md C:\mount\winre
Dism /Mount-Image /ImageFile:c:\mount\windows\windows\system32\recovery\winre.wim /Index:1 /MountDir:C:\mount\winre

From there you can choose to add third party drivers or list existing drivers. (If you list the existing drivers, then you will be a step closer in deciding if the problem resides in WinRE or Macrium Reflect.) For example
Dism /Image:C:\mount\winre /Add-Driver /Driver:"C:\SampleDriver\driver.inf"
will add driver.inf to mounted image located at path C:\mount\WinRE
While, Dism /Image:C:\mount\winre /Get-Drivers will list Third Party drivers installed in mounted image.

Once done, then you need to unmount the image, and commit any changes that you want to keep. See Customize Windows RE and DISM Driver Servicing (.inf) Command-Line Options for more details.
 

My Computer

System One

  • Operating System
    Windows 10

SD_83

New Member
Local time
7:19 AM
Posts
4
Thread starter
Saw your post at BC also - a suggestion there already by the mod, let us know if that helps or not.
Seen that.. would try with the newly released (3 days back) version of Macrium and report back..
He suggested rescue media. MR Rescue media & MR Restore from boot menu both had same issues.
 

My Computer

System One

  • Operating System
    Windows 10

SD_83

New Member
Local time
7:19 AM
Posts
4
Thread starter
As a matter of interest, how are you adding drivers to the driver store? Had you tried using DISM to add or query the drivers in WinRE?
If you first mount the Windows image with
md C:\mount\windows
Dism /Mount-Image /ImageFile:C:\mount\install.wim /Index:1 /MountDir:C:\mount\windows
where C:\mount\windows is the location of your offline Windows image.
Then mount the offline WinRE image with
md C:\mount\winre
Dism /Mount-Image /ImageFile:c:\mount\windows\windows\system32\recovery\winre.wim /Index:1 /MountDir:C:\mount\winre

From there you can choose to add third party drivers or list existing drivers. (If you list the existing drivers, then you will be a step closer in deciding if the problem resides in WinRE or Macrium Reflect.) For example
Dism /Image:C:\mount\winre /Add-Driver /Driver:"C:\SampleDriver\driver.inf"
will add driver.inf to mounted image located at path C:\mount\WinRE
While, Dism /Image:C:\mount\winre /Get-Drivers will list Third Party drivers installed in mounted image.

Once done, then you need to unmount the image, and commit any changes that you want to keep. See Customize Windows RE and DISM Driver Servicing (.inf) Command-Line Options for more details.
Thanks for a detailed insight. I would try that later next month and report back, thanks! 🙂

I had tried adding drivers by Macrium's Advance options while creating the Restore boot menu. There's scan option and folder can be specified. Also checked the override default drivers option there.. Confluence Mobile - Macrium Reflect Knowledgebase

Also came upon this: Enabling Surface Pro 3 Dock Gigabit Ethernet drivers in Windows PE

Looks like this is more a problem of GPT systems: Mouse and Keyboard not working in 7.2.4325 - (Page 5)

First, I will try latest version of Macrium from the scratch, as I mentioned; if not I will try deployment next month as you suggested; and report back. . Thanks!
 

My Computer

System One

  • Operating System
    Windows 10

SD_83

New Member
Local time
7:19 AM
Posts
4
Thread starter
Not really a solution but more of a workaround. On the problem PC create another rescue media using Windows RE this time.

View attachment 4070

A bit confused here as you say 'using Macrium PE for restoring images' but also say ' Native base Win RE version was used'.
Windows Preinstallation Environment is a lightweight version of Windows used for the deployment ... Windows Recovery Environment (WinRE) is a set of tools based on Windows PE.

The Recovery Media in General for Macrium is referred to as Macrium PE. It can be used for testing on any hardware, without Installation also for restoring images. In my case, the Windows Image File toolset used for building Macrium PE was base Win RE. I mentioned native because you don't need to download anything unlike WAIK or WADK. Base WIM of the OS is used.
 

My Computer

System One

  • Operating System
    Windows 10

Fabler2

Active Member
VIP
Local time
2:49 AM
Posts
133
Location
Wales, UK
Worth trying the PE 10 (WADK) option then if only to test if it works.
 

My Computer

System One

  • Operating System
    Win 10 Home
    Computer type
    Laptop
    Manufacturer/Model
    ASUS VivoBook
    CPU
    AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
    Motherboard
    ASUSTeK COMPUTER INC. X509DA (FP5)
    Memory
    8 GB
    Graphics Card(s)
    RX Vega 10 Graphics
    Monitor(s) Displays
    Generic PnP Monitor (1920x1080@60Hz)
    Hard Drives
    476GB INTEL SSDPEKNW512G8
    Internet Speed
    25 Mbps
    Browser
    Edge
    Antivirus
    Defender
Top