[Bob Blum]

Actually, it is Microsoft’s answer to Chrome OS, as used in the Chromebook.  YouTube video’s show it is being very similar, although more limited in functionality.  Microsoft originally planned it for fold-able devices, but has changed course and will now initially release it for laptops and desktops.

2 users thanked author for this post.

doriel, Microfix

[Bob Blum]

Al,

Not sure why that is happening. I did a Google search using the following search term: “Windows 10: The boot configuration data store could not be opened.”
At least one of the results suggests that you are on the right track in suspecting that it is a UEFI issue. It suggests changing to a “Legacy” boot mode to resolve the problem. Might be worth a try.

[Bob Blum]

Al,

See if this works, although it will disable your F8 capability:

Go to the command prompt with administrative privileges;

At the prompt, enter the following statement:
BCDEDIT /SET {DEFAULT} BOOTMENUPOLICY STANDARD

Depending upon the computer, the BIOS options may only appear when booting from a complete shutdown, not during a re-start.

Hope this helps.

[Bob Blum]

If you use the BCDEdit codes, it has not simplified the access to Safe Mode, which I viewed as the purpose of the BootSafe utility.  What is needed is to access Safe Mode from a computer that will not complete the full boot into Windows.  The triple restart process is one option, but doesn’t always work on all computers.

[Bob Blum]

In search box in lower left corner of taskbar, type “netplwiz” (without the quotes).  Uncheck the box “Require password for this account.”  Click Apply.  Enter your password to confirm that you are really the owner of the account.  And your done.  You actually still have a password, but you are now able to bypass it when booting the computer.

[Bob Blum]

Fed,

Which TPLink product did you use?   Which version?

 

[Bob Blum]

Try booting from a flash drive with Linux on it (i.e., a “live” flash drive).  If the problem still occurs with Linux, you’ll know that it is a hardware problem, rather than a Windows problem.  If the problem does not occur with Linux, I would do two things in Windows:  run chkdsk c: /f, to clear up any corrupted file system entries.  Secondly, uninstall Bit Defender, at least temporarily, to see if that resolves the problem.  I’ve seen several problems resulting from misbehaving Bit Defender.  Don’t know if Bit Defender was really the culprit or whether it was just a coincidence.

[Author]

Posts