Windows 10: Win10 Vol4

Win10 Vol4?
Recently finished upgrade install from 8.1 pro to win10; all seemed normal but I did not turn system protection on, ergo no win 10 restore point but do have win 8.1 restore point.

Installed VS community 2015 (free version) which required a restart.

At startup, 2 versions of win10 showed up

Default was…win10 vol4; this started OK and I could run program including the VS community 2015
Option was…win10; starts to load but stops at blue screen which is displaying the following:

Recovery
Your pc needs to be repaired. The app or OS couldn’t be loaded because a req’d file is missing or has errors.

File:\windows\system32\winload.exe
Error code: 0xc000000e
You’ll need to use recovery tools. If no install media contact pc admin etc.

Press enter to try again (did, no response)
press F8 for startup options (again no response)
press F9 to use diff OS (this restarted the system)
end of message

In disk management: all looks normal
In file explr win10 vol4 c: drive shows
$windows.~BT
$windows.~WS
My files
Windows
Windows.old
Posting to get some help on best approach to T/S this problem.

:)

 

HP laptop screen is completely black. Windows 10 upgrade was in process.

Product Name: HP compaq presario laptop CQ56-DX115

Operating System: Microsoft Windows 7 (64 bit)

I have seen this problem before with my laptop. Under Windows 7, I would simply perform a hard reset and my laptop would then boot up Windows 7. Over the past few years, I have only had to do this two or three times.

Yesterday, from the task bar tray at the bottom of my Windows 7 desktop, I found that my free Windows 10 upgrade was available from Microsoft and that an installation could be scheduled. I followed all the prompts until I reached the Windows 10 upgrade
screen that said "Working on it" with a large spinning icon. I waited for several minutes when I assumed that it was probably loading the new OS. I left my laptop alone for the remainder of the day. I have a comcast cable wifi connection.

Today I went to start my laptop and I can hear the fan, and the usual self-test noise from one of the drives, but nothing at all on the screen. Pitch black. I pressed the power button to shut off. Then I pressed it again to start. I can hear the fan and
one of the drives in self-test, but there is never anything on the screen at any moment. No cursor, logos, absolutely nothing.

I performed a hard reset according to instructions provided by HP's website. Additionally, I have noticed that the caps lock button blinks in a manner that communicates "CPU not functional" according to HP's blinking light code table.

So I went back to HP's website and followed instructions for recovering the BIOS. I now have my laptop working again and I'm back to the Windows10 "working on it" screen. I have read that this process may take more than 24 hours.

After approximately 3 days, Windows 10 installed but the desktop screen flashed constantly. I'm going to look for my restore disc and go back to Windows 7 for the time being.

 

How to start win10 in safe mode? (system thread exxception not handleed)

Hi,

I was watching movie last night and suddenly Computer crashed.

I tried to restart it and had an error message that compuer crashed and needed to restart. Restart will occur automaticully. Now I'm stuck in a restarting loop again and again and again.

I tried to enter safe mod dy hitting F8 while starting but it did not work. I also triedthree times to restart and shut down, but that did not work either.

Any ideas what to do next?

 

Sounds like an extra boot file got loaded on to the boot loader.

A temporary fix would be to go into the working operating system. Click on cortana, type, msconfig, open msconfig, go to boot tab, and set the vol4 as the default OS. Click apply and reboot.

Only apply the default OS to the working Windows 10.

You may need to back up your files and do a reinstall, but maybe someone else may be of better assistance

That is odd that happened.

 

thanks for reply. I'm hoping to get more inputs before I take any action but I will explore your suggestion.

 

Then after you are sure the default OS is booting fine, just go back into MSCONFIG and delete the extra entry for the non-default, non-functioning entry and you have a permanent solution. No need for a re-install.

 

Restart
boot screen shows next to the buttons

win10
on vol 4

win10

I click on button 1, the "on vol 4" button

Once running, run msconfig and on the general tab
it has selected "selective startup"
checks on load systems services and load start up items
Use original boot configuration is grayed out.

boot tab shows

Windows 10 (C:\windows):current OS;Default OS
Windows10 (\windows)

I tried to change the general tab to normal startup and use the "original boot configuration" but after a restart
msconfig had returned to the "selective startup"

suggestions needed
tom

 

It does that. After they moved the startup tab to Task manager in Windows 8, that has been a little buggy. Windows 10 is the same way, although MS released a fix on Windows 8.1 to fix that issue, but it only affected new installs that was a clean install. Current installed systems were not affected by the update.

I upgraded from Windows 7 to Windows 8, and that was a constant problem with msconfig. Also upgraded from Windows 8 to 8.1, and things only got worse from there as nothing worked correctly. I couldn't even create a system image due to the functionality being broken.

The only thing that fixed everything was when I install a clean Windows 8.1 PRO with Update 1 included. Everything worked well.

Msconfig has worked for me on clean installs only, but there may be others who's have worked correctly after upgrade.

Some have found workarounds but I prefer not to do that.

 

apparent that not many want to fool with the MBR. But I found this one
http://www.thewindowsclub.com/repair...rd-mbr-windows

But I am inclined to just live with this as long as thee are no further complications. If there are, well then, clean install.

 

LtCmdr; that did help o;n the boot but msconfig is still not going to normal boot. beginning to think Imaneke is right, that msconfig is having problems with boot. I am most likely to do a clean install and if it gives me a stable result I'll let you know. I did try the corrections in the link I posted but, as with this solution, msconfig is only good until the second restart. Odd; seems like it's a switch.

 

I think you're correct; a clean install is best solution.
But the Commander's deletion idea does eliminate the start option. It goes right into the working install.

 

If his solution worked, I would keep the working install going, but if you choose to reinstall, make sure to backup your files. You can also create a system image if you choose to.