cdob

A additonal hint: Windows 10 1803 home is supported up to November 12, 2019. https://support.microsoft.com/en-us/help/13853/windows-lifecycle-fact-sheet I would try a clean installation with Windesk9+3G_V2_Windows_10_1803x86_FAT32.iso And do a upgrade to 1903. Keep in mind: this is a automatic repair installation with preserving the user data. Read: technically a new windows 10 1903 installation. The Bay Trail drivers are automatically reused from the 1803 installation. Should work, may fail. Be aware, with a Bay Trail CPU, 1 GB RAM and a emmc drive: Expect a day to do this. 1909 is arround the corner. This is more like a 1903 SP1: updates, not a new windows installation. If 1903 works well, the 1909 should work too.

@HadroLepton Which model number do you use? There are manufacturer "Windows Image & Treiber" https://www.odyshilfe.de/treiber Added: It's a Bay Trail hardware. Intel dosn't support this anymore, there are Windows 8.1 drivers. https://www.intel.de/content/www/de/de/support/articles/000006105/processors.html The 8.1 driver works at Windows 10 1803, may work or fail at Windows 10 1903 or later. There is a Windesk9+3G_V2_Windows_10_1803x86_FAT32.iso for the X610129 device. There are Bay Trail drivers included in boot.wim and install.wim. Create a USB Stick, use FAT32 filesystem. Install Windows 10. In case if you like to use more recent 1903 x86: There are no bay trail dirvers at a vanilla 1903 ISO, hence no internal keyboard. Try the drivers from the Odys Windesk9+3G_V2_Windows_10_1803x86_FAT32.iso use a USB OTG cable, a USB Hub, USB mouse and USB keyboard. Install the Bay trail drivers, the internal keyboard works now. Or try similar hardware. https://downloadcenter.intel.com/download/25311/System-on-a-Chip-SOC-Driver-Package-for-STCK1A32WFC https://downloadcenter.intel.com/download/26693/NUCs-System-on-a-Chip-SOC-32-Bit-Driver-Package-for-Intel-NUC

MBR USB boot testings: Some real world testings at a Thinkpad X230. Given a 3 TB USB hard disk with 512e bytes per sector. Three partitions: USB_BOOT, USB_2TB, USB_data USB_BOOT: a primary active FAT32 8 GB USB_2TB: NTFS 2 TB, within first 2 TiB of the hard disk USB_data: NTFS, behind 2 TiB 13 80 0 32 33 1023 254 63 2048 16580608 16582656 partition end sector on disk 7 0 1023 254 63 1023 254 63 16582656 4278384632 4294967288 partition end sector on disk 7 0 1023 254 63 1023 254 63 4294967288 1565499400 5860466688 partition end sector on disk 5860466688 sectors on disk BIOS mode, grub4dos geometry (hd0) drive 0x80(LBA): C/H/S=267350/255/63 Count/Size=4294967289/512 Partition num: 0, active, Fileystem type is fat32, partition type 0x0C Partition num: 1, Fileystem type is ntfs, partition type 0x07 Partition num: 2, Fileystem type is unknown, partition type 0x07 cat --hex (hd0)4294967296+1 correct hexdump, does match the hard disk sector. The BIOS reads up to 2 TiB. cat --hex (hd0)4294967297+1 zero listed only, dosn't match the hard disk sector The BIOS fails above 2 TiB. Bios boot, installation is possible: Windows 10 files at first partition Windows 10 \boot and \sources\boot.wim at first partition, \sources\install.wim at second partiton Windows 10 \boot and \sources\boot.wim at first partition, \sources\install.wim at third partiton: PE reads the whole disk Windows 10 \boot at first partition, \sources\boot.wim at second partition, \sources\install.wim at third partiton: \boot\bcd is adjusted to read \sources\boot.wim at the second partition booting fails: bootmgr message: A required device isn't connected or can't be accessed. Windows 10 \boot at first partition, \sources\boot.wim and \sources\install.wim at third partiton: \boot\bcd is adjusted to read \sources\boot.wim at the third partition Yes, the BIOS dosn't acces the whole disk, hence the bootmgr message. There are the equal results at UEFI boot. Even at UEFI moode, the first 2 TiB can be accessed only. There is either a UEFI limitation or bootmgfw.efi is limited. There may be other UEFI results at another hardware.

There is a special BIOS. Use a adjusted ntdetect.com https://web.archive.org/web/20060302092406/http://www.911cd.net/forums//index.php?showtopic=14181

At NT times, set the path to batch.cmd drive and path: batch.cmd cd /d %~dp0 or another relative path cd /d "%~dp0..\folder" cd /d "%~dp0folder" Does this works still?

Verify the used storage controller, use the AMD SATA controller. Boot XP at IDE mode, copy driver file ahcix86.sys and set registry. Set AHCI at BIOS next.

Repair or remove programs in Windows 10: https://support.microsoft.com/en-gb/help/4028054/windows-10-repair-or-remove-programs Select the Start button, Settings and Apps.

Can you uninstall the WinZip privacy protector app?

Vmware Player does run a 32 bit XP system. A USB scanner can be passed from a 64 bin Win7 to the XP system.

It's no the RAM itself, something before the RAM. E,g broken capacitors or power supply. At a old machine, capacitors may dry out, without a bulking head. Ignore the error so far, replace the hardware in future.

There are some minor trouble, yes this can result to a BSOD 0x7e. Backup importand data first. Run a extended test at WD windlg.exe. If there is a question to repair at end of test, do the repair. https://support.wdc.com/downloads.aspx?p=3&lang=en

Nvidia offers XP drivers still. Overall it's a hit or miss. May work or fail finally. XP should run at the EliteDesk 800 G1. However expect a driver hunting, may take some time. And exppect minor glitches, e.g. already mentioned missing USB3.0 Good luck

https://support.hp.com/au-en/document/c03832938 HP EliteDesk 800 G1 Small Form Factor (SFF) PC Specifications Chipset Intel Q87 Express Windows XP is not supported by the manufactuer. XP should run at a Q87 in general, however it's a search for the drivers. SATA, chipset and network should be possible. Which graphic card is installed? No USB 3.0 drivers, change BIOS to USB 2.0 mode.

Without the driver the cpu runs at full speed. Power scheme cannot reduce the speed, there is no cpu power driver. I guess stock speed 3.5 Ghz, I don't know Fx cpu details, hence 3.8 Ghz is possible too. Try the driver.

A amd processor driver was required to change the processor speed (amdk8.sys) back then. Date: 10/02/2007 http://m.majorgeeks.com/files/details/amd_k8_processor_driver.html The old driver may work or fail at the FX cpu.

No, the USB get's a drive letter at textmode normally. As far as I know, the Rufus MBR at USB does addional settings, like drive swapping. I don't remember details. Didn't get hard disk second partiton the d: drive letter at textmode? Is this with or without a migrate.inf? Does this change at installation? Which hardware do you use? There are some strange BIOS releases.

@shae Try both: set a drive letter for the USB partition. And set drive letter d: for the hard disk partiitons in addition. Or boot a PE after first reboot. Import the XP registry system hive. And adjust MountedDevices, rename e: to d: Raw example, to be adjusted https://support.microsoft.com/en-us/help/223188/how-to-restore-the-system-boot-drive-letter-in-windows

I understand, you did save the Legacy Only setting. That's good. Did you try to boot from the pendrive? Do this. What do you get next? Does Win8.1 installation start?

@Togijak Add files StartDot3.VBS, USERDATA-EAP-TLS.xml and Wired-WinPE-EAP-TLS.xml too. https://support.microsoft.com/de-de/help/972831/the-ieee-802-1x-authentication-protocol-is-not-supported-in-windows-pr https://support.microsoft.com/en-gb/help/972831/the-ieee-802-1x-authentication-protocol-is-not-supported-in-windows-pr

Can you check this at a machine? I get at Win 10, VMware UEFI boot: bcdedit /set {bootmgr} description "NVRAM run \EFI\Microsoft\Boot\bootmgfw.efi" The VMware nvram file contains the unicode string "NVRAM run \EFI\Microsoft\Boot\bootmgfw.efi". UEFI boot selection shows ths string too. Bcdedit does write to UEFI NVRAM. Can you clarify your project? A default windows installtion dosn't set the [firmware device name]. Which part sets the [firmware device name]? Or does the motherboard add the [firmware device name] on the fly?

@i430VX Isn't this a Atom Z3735G bay trail hardware? The touchpad is connected to a IO controller. Do you have a OTG cable and a USB mice? Install the IO drivers first Or embedd the relating IO drivers to Windows 8/10. https://downloadcenter.intel.com/product/29035/Intel-Atom-Processor Processor I/O Controller Driver https://downloadcenter.intel.com/download/24096/Intel-Processor-I-O-Controller-Driver-for-Windows-8-1- https://downloadcenter.intel.com/download/25618/Intel-Embedded-Drivers-for-Microsoft-Windows-10-IoT-Core-32-bit-and-64-bit-MR1?product=29035 Or search at big manufacturer for bay trail hardware. They may offer drivers (chipset / IO) .

A D820 uses a 945GM chipset. https://www.dell.com/downloads/global/products/latit/en/spec_latit_d820_en.pdf 26 W is average for this hardware family. Which CPU and graphic card do you use? RMClock Utility can change CPU VCore. http://cpu.rightmark.org/download.shtml However the limitations are hard wired at the CPU. A average mobil CPU runs at a lower voltage too. https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors Undervolt the CPU at low speed http://forum.notebookreview.com/threads/undervolting-core-duo-core-2-duo-by-pin-mod-part-2.365230/ Do you use a NVida GPU? Undervolt the GPU http://www.guru3d.com/files-details/nvidia-inspector-download.html Given little CPU being used, no need to remove a lot of programs. The programs seems not to produce CPU load. Do you use a virus scanner? Remove this at a internal network machnie. Given a 945GM hardware area, some power reduction should be possible, but not very much (not half power consumption). I guess the challenge is with given hardware. Disable devices at device manager or remove not used hardware, e.g. Bluetooth, WLAN, Modem http://downloads.dell.com/manuals/all-products/esuprt_laptop/esuprt_latitude_laptop/latitude-d820_service%20manual_en-us.pdf

VIA USB 3.0 driver xhcdrv.sys calls windows driver wdfldr.sys. If you use a historic VIA USB 3.0 driver , it's calling a wdfldr.sys 1.9. This wdfldr.sys is integrated in Windows 7. The xhcdrv.sys driver works. Dism includes the VIA USB 3.0 driver only, not the WdfCoInstaller. The OS default wdfldr.sys is used still. If you use a current VIA USB 3.0 driver, then xhcdrv.sys calls a newer wdfldr.sys. This is not included in Windows 7. The xhcdrv.sys driver dosn't works. The system is calling for a missing driver. It's a driver version conflict. If you install the drivers at windows, then WdfCoInstaller is installed too. There is a current wdfldr.sys installed. The xhcdrv.sys driver works. If a user use historic hardware, the historic VIA driver works. If a user use more recent hardware, the historic VIA driver dosn't support the hardware and fails.

This is a historic VIA driver with WdfCoInstaller01009.dll. Yes, Windows 7 supports this WDF 1.9 version out of the box. Congratulations, the old drivers works at given hardware.

VIA USB 3.0 is a WDF driver model. The culprit is the Wdf driver version. At 4.50 it was a WdfCoInstaller01011.dll. Which version uses 4.90A? Windows 7 supports WDF 1.9 out of the box. https://docs.microsoft.com/en-us/windows-hardware/drivers/wdf/kmdf-version-history If you like to install from USB, there is no need to set start mode. Booting from USB is another case. What about post #7? http://reboot.pro/topic/21231-can-w7-be-booted-from-usb30-port/#entry200513 Be aware, there are CPU requirements. A Win 8.1 install ISO may be useful. There is 'dism /apply-image' and 'bcdboot' out ot the box.