Windows 10 cannot read the installation media USB

Hello, Paloma.

Thanks for the suggestions dated Sep.25 2021.

My guess:

A. The OS of the dead-locked PC cannot read the installation media USB.

B. Due to this, any or all kinds of media USB is useless.

Reason for suck a guess:

The reactions when the USB is plugged in the dead PC & when the power of the dead PC is on:

1. The light of the USB is on but not flashing which means not communicating with the OS,
2. There is no any indication showing the OS reads the USB, a sound, blink, flash, message . . . .

About Rufus.

Does Rufus initiatively communicate with the OS of the dead locked PC if an installation media USB is made by Rufus & if the USB is plugged into the PC ?

My guess again:

Need something that can initiatively communicate with the OS of the dead locked PC. & then conduct a re-installation.

What do you think?

"Try unplugging all disks by removing the cables and verifying that startup exits this screen." You said. I do not understand this. "Try unplugging all disks by removing the cables" is understood, but "verifying that startup exits this screen." is not understood. Explain it, please?

Thanks.

Chuenmon

Is this PC a brand name system? Dell, HP, Acer, etc? If so, look up information on how to enter the "boot menu" manually. For example, you would hit one of the following keys, F2, F9, F10, and like my Dell laptop F12. A boot menu will be displayed and show you the connected device to boot from (the boot order). The HDD, USB, etc. If you get that far, you want to boot from the USB stick of which you created from your Windows 7 computer. If your lucky the installation process will start. Since you say you see the light on the USB stick blinking, you have power in the USB port.

Thank you, LintekPC.

"Is this PC a brand name system?"

Yes. It is an Acer.

"If so, look up information on how to enter the "boot menu" manually."

I'm not sure I understand what you mean.

No matter how you do anything to the PC, automatically or manually, the OS must respond to whatever you do. At the moment, the OS of the dead PC does not respond to anything I do to it.

"Since you say you see the light on the USB stick blinking, you have power in the USB port."

Most flash sticks have a light indicator which lights up if there is power on. This light on indicator tells that it is connected to the device or PC but not communicating with the system of the device or PC unless the indicator is flashing or blinking. I said in my last post that the light indicator of the USB is not flashing or blinking.

Appreciate your goodwill trying to help.

Chuenmon

Are you saying, when you turn the power on to the PC, nothing happens? Not even the fan starts? No power at all? That's the meaning of a "dead" system. If you are getting power, then try a different USB port.

This is a sample image of a boot menu. When you hit one of the F* keys I described, this is what the PC will present to you. And if you see the USB device you would select it to start.

You did create the installation media correctly on the USB stick? Maybe that's your problem.

Another example:

It was nothing Chuenmon, it's a pleasure to be able to try to help you.

As for Rufus it is just an alternative method for creating the USB.

From what I understand from the descriptions you provided, there are no problems with the installation media, that is, in this situation none will work, as you cannot access the motherboard BIOS to configure your computer's startup.

There is a hardware problem with your computer, causing it to lock up and not even be able to start the BIOS.

As for your question, let me try to explain again.

You should test, disconnect everything from the motherboard and after that turn on the computer, and analyze if it will get stuck on the same screen, or switch to another one, try also pressing the BIOS access screen and check if it enters the settings of the BIOS or not.

Anyway, I believe it's best if you take this computer to a local service you trust so they can perform a deep hardware check to better identify this issue.