Windows 10: Windows 10 will not boot after installing .NET update

Hi all! I'll get straight to it. I performed windows updates on my wife's PC, which does not get used very much at all. After installing said updates, the PC prompted for a restart to finish installation needed to install a .NET framework. Shut down went well, 100% completion of update install. Now when PC restarts, I get my ASUS splash screen, messages at bottom diagnosing your PC...attempting repairs, and then a blue main screen with the options of:


1> Continue to Windows does not work, just brings me back to the blue screen again


2> Use a device not sure what I would need to do with this option


3> Troubleshoot Have tried several of these, including system restore, uninstall updates, both the latest quality and feature update, startup repair, and PC reset...none of these work


4> Turn off your PC seems to work just fine...


Not sure where to go from here, would appreciate some help.


Running Win 10 Home 64 Bit.

:)

 

Windows 10 USB boot

Hi there, am not a windows 10 expert. I have a pc in the bedroom on windows 10, I messed up the bootloader trying to fix the xp on that system.

System wont boot, trying to repair via win 10 usb installer.

Downloaded the media creation tool to install windows 10 installer on usb stick. Not compatible with a host of usb sticks I have. Tried the usb sticks that others use, but I think they use rufus; as the media creation tool by win 10 does not detect the usb stick.

So quick question, the win10 machine i am trying to repair the bootloader is a win7 upgraded to win10.
If i were to use the usb win10 installer to "repair installation" does the version of the iso downloaded via the media creation tool matter?

There is three options:
Windows 10
Windows 10 Home
Windows 10 N

Also is there a step by step instead of using rufus as I want to try an alternative method of creating a usb win 10 installer. Preferably with more compatibility.

System is a asus sabertooth 990 (r2?) with AMD phenom X 6.

Also is there any other software I can load onto the usb that can repair the bootloader easily?
That would be the ideal alternative. Thanks

 

New install Windows 10 (issue solved)

It's good that you're not experiencing any issues. Unfortunately many folks are, a quick Google search will show the same info im offering the OP.

Heres a couple examples:

Here

Here

It's basically what I mentioned above, small issues here and there ,but nothing to end your day.. for the most part.

I know it's anecdotal, but for my experience 95% of the time it's perfectly fine. The issues I've run into wouldn't be enough for me to roll back , but they would be enough (had I not installed it yet) ,to avoid it for another couple weeks which is why I'm suggesting it to the OP

Windows 10 Fall Creators Update problems and complaints

• Installation problems with the Fall Creators Update
• Microsoft Edge problems with the Fall Creators Update
• Drivers problems with the Fall Creators Update
• Experience problems with the Fall Creators Update

keep in mind, as of recently, the FCU is installed on 5% of devices roughly.....

 

Windows Updates failed to instal

I'm not sure how differant XP media center Edition is but you could clear the history \ cache if these folders are there.

Step 1 Register DLL files.

=================

By trying this step, we can check if the update engines are working properly.



1. Close all instances of Internet Explorer.

2. Click Start and Run, type "Regsvr32 atl.dll" (without quotes) in the Open box and click OK.



Note: There is a space between regsvr32 and atl.dll



3. Similarly, one by one, register the files listed below:



Regsvr32 msxml3.dll

Regsvr32 wuapi.dll

Regsvr32 wuaueng.dll

Regsvr32 wuaueng1.dll

Regsvr32 wups2.dll

Regsvr32 wucltui.dll

Regsvr32 wups.dll

Regsvr32 wuweb.dll

Regsvr32 qmgr.dll

Regsvr32 qmgrprxy.dll

Regsvr32 jscript.dll



Note: If you encounter errors while registering any of these files then skip that file and continue with the next one.



If the issue persists, let's move on to the steps below to verify Windows Update services and temporary folders.



Step 2 Verify the relevant Windows Update services.

=========================================

1. Click Start->Run, type "services.msc" (without quotation marks) in the open box and click OK.

2. Double click the service "Automatic Updates".

3. Click on the Log On tab, please ensure the option "Local System account" is selected and the option "Allow service to interact with desktop" is unchecked.

4. Check if this service has been enabled on the listed Hardware Profile. If not, please click the Enable button to enable it.

5. Click on the tab "General "; make sure the "Startup Type" is "Automatic" or "Manual". Then please click the button "Stop" under "Service Status" to stop the service.

6. Then please click the button "Start" under "Service Status" to start the service.

7. Please repeat the above steps with the other services:



Background Intelligent Transfer Service

Event Log

Remote Procedure Call (RPC)



Note: Event log service is enabled on all of the hardware profiles; this service does not have an option to enable or disable on certain hardware profile.



If it still does not help, let's proceed to step 3.



Step 3 Reload the Update temporary folders.

===================================

One possible cause is that the temporary folder for Windows Update is containing corrupted files. Let's erase all the files there to get the system clean.



1. Click Start, Run, type: cmd and press Enter. Please run the following command in the opened window.



Net stop WuAuServ



2. Click Start, Run, type: %windir% and press Enter.

3. In the opened folder, rename the folder SoftwareDistribution to Sdold.

4. Click Start, Run, type: cmd and press Enter. Please run the following command in the opened window.



Net start WuAuServ



Please test the Windows Update website and let me know the result. If the issue persists, to clarify the issue and provide more accurate troubleshooting steps, please assist me in collecting the following information.