Windows 10: PXE environment

Hello...

buddy dropped of a PC that his work got rid of.

The BIOS shows PXE (Preboot exe environment) as the boot protocol.

How do I change this? Once you get out of the BIOS it says no active partition. I assume this means that this PC is config'd to boot on the network. It shows the MAC addy in the banner screen upon boot up.

:)

 

PXE-E61 MEDIA TEST FAILED, CHECK CABLE PXE-MOF EXITING PXE ROM

Hi,

I am getting the following error on my
Dell Studio 1747

PXE-E61 MEDIA TEST FAILED, CHECK CABLE

PXE-MOF EXITING PXE ROM

The hard drive is seen when I hit F2 and look at the specs

I have taken the hard drive out and reinstalled. It did not help but the computer still recognizes the hard drive.

Any suggestions?

 

System environment variable won't stick

Running Win10 Home on an Acer Spin 3, 64bit, i7cpu. I try to add a path to the system environment variables by:

1. Control Panel > System > Advanced system settings > Advanced tab > Environment variables

2. The "Environment Variables" window opens.
3. In the "System Variables" pane I select "Path" and click the EDIT button.
4. A list of the current system paths is displayed.
5. I click the NEW button, browse to the path I want to add which is "C:\Python36-32" and click OK. The path "C:\Python36-32" is added to the list of current system paths.
6. I click OK and am returned to the "Environment Variables" window.
7. I click the "X" at the top right to close the "Environment Variables" window.

Now if I click the "Environment Variables" button again (end of step-1) and repeat steps 2-4, the new path I added in step-5 is gone. IOW, adding a new path won't stick.

What am I doing wrong?

 

From yesterday my PC Toshiba Satellite -L450-16Q write this message and don't start. PXE-E61: Media test failure, check cable; PXE-M0F: Exiting PXE ROM. A disk read error occurred; Press Ctrl+Alt+Del

PXE (Preboot Execution Environment) is a micro operating system built into the network card. It allows the card to request and accept an IP address issued by the network and then ask for any server that has an operating system available to boot its host
computer. It allows computers that have no operating system internally to boot from a network server. This is very specialised and seldom seen outside large networks.

PXE is one of the possible devices a computer can start from such as Floppy, Optical disk, USB Flash drive or the hard disk. The boot order is the set list of which devices will be tried in sequence. As each one in the list fails it moves onto the next.
So FDD > CD > USB >HDD > PXE would mean that normally the 1st 3 would try and fail before booting from the hard disk

There are two reasons why PXE would appear. The order gets mixed up so PXE is tried before the HDD, it times out because there is no server or as on your case the LAN card has no cable. Then it would go onto the HDD.

Alternatively the HDD times out so it moves on to the next device. You are right to be concerned because this is more than just corrupt Windows. In that case the drive accepts the boot so it would not step on to PXE but would generate either file corruption
messages or "Missing Operating System"

The "A disk read error occurred" indicates it cannot read the boot sector itself. Hopefully that is all that is a problem but it could be more serious. Normally the next option would be to boot from Windows media and attempt a repair but that involves making
changes to the disk which MIGHT compromise recovering files if they are important.

I would recommend making no changes to the disk, instead remove it from the computer. Use a USB adapter to plug it into another PC and see what can be read, that may give you the opportunity to recover important files before anything else is tried.