HP ProBook 655 G3 - Cannot install windows 10 32 bit on 64 bit

[styf6]

I have laptop HP ProBook 655 G3 with Windows 10 Pro 64 bit. I need to instal 32bit version of Windows 10 on this computer, but when I boot instalation USB and choose to install 32 bit version, the pc show me this error:

_______________

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:

      1.   Insert your Windows installation disc and restart your computer.

      2.  Choose your language settings, and then click "Next."

      3.  Click "Repair your computer."

If you do not have this disc, contact your system administrator or computer manufacturer for assistance

          File: \windows\system32\boot\winload.efi

          Status: 0xc0000359

         Info: The application or operating system couldnt't be loaded because a required file is missing or contains errors.

________________ 

USB is made with Media creation tool from official Microsoft page for both versions, 64 and 32 bit. 

Anyone can help?

[Ruben_S]

Hi, Cause :

---

The issue occurs because the binary file is the 32-bit version and it needs to be replaced by the 64-bit version.How to fix

To fix the issue, follow these steps.

Step 1: Attach the OS disk of the VM to another VM as a data disk

1. Delete the virtual machine (VM). Make sure that you select the Keep the disks option when you do this.
2. Attach the OS disk as a data disk to another VM (a troubleshooting VM). For more information, see How to attach a data disk to a Windows VM in the Azure portal.
3. Connect to the troubleshooting VM. Open Computer management > Disk management. Make sure that the OS disk is online and that its partitions have drive letters assigned.

Step 2: Replace the corrupted file

1. On the attached disk, browse to the location of the binary file that's displayed in the error message.
2. Rename the file to <BINARY.SYS>.OLD.
3. On the attached disk, browse to the \Windows\winsxs folder. Then, search for the binary file that's displayed in the error message. To do this, run the following command at a command prompt:

   dir <binaryname> /s 

   The command lists all the different versions of the binary file together with the created date. Copy the latest version of the binary file to the windows\system32 folder by running the following command:

   copy <drive>:\Windows\WinSxS\<directory_where_file_is>\<binary_with_extension> <drive>:\Windows\System32\Drivers\ 

   
   For example, see the following screen shot.
   
   
   
   
   
   Notes 
    
   • The screen shot shows volume E. However, the actual letter will appropriately reflect the one of the faulty drives (the OS disk attached as a data disk on the troubleshooting VM). 
   • If the latest binary doesn't work, you can try the previous file version to obtain an earlier system update level on that component.
   • If the only binary that's returned in this step matches the file that you're trying to replace on the affected VM, and if both files have the same size and time stamp, you can replace the corrupted file by copying it from another working VM that has the same OS and, if possible, the same system update level.
4. Detach the repaired disk from the troubleshooting VM. Then, create a VM from the OS disk.

"I work for HP."
Regards,
Ruben
****Click the (purple thumbs up icon in the lower right corner of a post) to say thanks****
****Please mark Accept As Solution if it solves your problem****