Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Computer will not boot back to window 10 after Microsoft window update


  • Please log in to reply
30 replies to this topic

#1 Sherif06

Sherif06

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 03 February 2017 - 01:41 PM

Hello,

My computer will not boot to window 10 after a Microsoft window update. I cannot restore back to earlier point or start the computer in safe mode  and startup repair does not work.  The only thing that I can get to is the command prompt. Please help.

 



BC AdBot (Login to Remove)

 


#2 JohnC_21

JohnC_21

  • Members
  • 24,676 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:09 PM

Posted 03 February 2017 - 02:23 PM

If you have a command prompt follow the steps shown using the DISM command.

 

http://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image



#3 technonymous

technonymous

  • Members
  • 2,520 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:09 PM

Posted 03 February 2017 - 02:26 PM

John beat me to it :P



#4 Sherif06

Sherif06
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 04 February 2017 - 10:12 AM

Thanks for your response guys. I have tried the DISM command  repair utility in the link.

Here the is the message I got:

Error : 87

The cleanup-image option is unknown.



#5 JohnC_21

JohnC_21

  • Members
  • 24,676 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:09 PM

Posted 04 February 2017 - 10:40 AM

That usually indicates the command was not inputted correctly. Make sure you have the correct spaces.

 

https://www.eightforums.com/performance-maintenance/36366-error-87-online-cleanup-image-restorehealth-option.html



#6 Sherif06

Sherif06
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 04 February 2017 - 12:44 PM

Hello

Here is pic of my screen when I used the DISM command. Now it showing error 50.Thanks.Attached File  20170204_113557.jpg   101.89KB   0 downloads

 



#7 JohnC_21

JohnC_21

  • Members
  • 24,676 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:09 PM

Posted 04 February 2017 - 03:14 PM

Your command prompt was started at boot and not using a Windows 10 install disk, correct? If your command prompt is started from boot and not through a boot disk then see this page.

 

https://appuals.com/best-fix-error-50-dism-does-not-support-servicing-windows-pe-with-the-online-option/

 

If you are using an install disk to arrive at command prompt then you need to use the source option. See the page I linked to in my previous post.



#8 Sherif06

Sherif06
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 04 February 2017 - 07:32 PM

Hello ,

Here is the pic of the message I got using DISM.

Attached File  20170204_182730.jpg   98.17KB   0 downloads



#9 technonymous

technonymous

  • Members
  • 2,520 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:09 PM

Posted 04 February 2017 - 07:47 PM

You should try going into the bios and reset it back to factory defaults and then try rebooting the system and/or the DISM command. It's possible that a hard drive setting (mode) in the hard drive section has changed ahci versus ide might have something to do with it. That has been an ongoing issue.



#10 technonymous

technonymous

  • Members
  • 2,520 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:09 PM

Posted 04 February 2017 - 08:23 PM

try source command. Something like this, but replace D with your cd drive letter.

 

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Install.esd



#11 Sherif06

Sherif06
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 04 February 2017 - 08:44 PM

I have reset my computer Bios to factory default and used the DISM command above I still get the same error as the pic I sent you earlier.  Thanks.



#12 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:07:09 AM

Posted 05 February 2017 - 12:19 AM

Hi Sherif06,

 

 

What happens after Windows boots do you get any error message?

Have you check the log file of Startup Repair (Automatic Repair) tool the log file can indicate what is causing Windows not booting.

Please execute below commands one at time and for each command you typed press Enter key.

Ren  C:\windows\system32\config\SAM         SAM.BAK
Ren  C:\windows\system32\config\SYSTEM      SYSTEM.BAK
Ren  C:\windows\system32\config\SECURITY    SECURITY.BAK
Ren  C:\windows\system32\config\DEFAULT     DEFAULT.BAK
Ren  C:\windows\system32\config\SOFTWARE    SOFTWARE.BAK
 
Copy  C:\Windows\System32\config\RegBack\SAM         C:\windows\system32\config
Copy  C:\Windows\System32\config\RegBack\SYSTEM      C:\windows\system32\config
Copy  C:\Windows\System32\config\RegBack\SECURITY    C:\windows\system32\config
Copy  C:\Windows\System32\config\RegBack\DEFAULT     C:\windows\system32\config
Copy  C:\Windows\System32\config\RegBack\SOFTWARE    C:\windows\system32\config

Above commands renames the registry files at their existing location, and then copies the registry files from the RegBack folder to the C:\Windows\System32\Config folder.

This procedure assumes that Windows 10 is installed to the C:\ partition. Make sure to replace C:\ drive letter to the appropriate Windows OS installed partition drive letter if it is a different location.

When computer boots into WinRE environment the drive letter assign to Windows partition may not be C: drive letter because Windows 7, 8 , 8.1 and 10 creates a separate system partition when it's installed from scratch. The system partition contains boot files WinRE assigns the system partition the C: drive letter and the Windows installed partition will be assign any other drive letter usually D: drive letter is assign to Windows installed partition. The Bcdedit /enum | find "osdevice" command can be use to find out the drive letter of the Windows installed partition the output of the Bcdedit command is similar to this osdevice partition=D:. The drive letter after partition= is the drive letter of the Windows partition.

Restart your computer to find out if Windows boots normally.

 


 


Posted Image


#13 Sherif06

Sherif06
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 05 February 2017 - 12:36 PM

Thanks for your help and response. I have copied the above commands and restart my computer. My computer did not boot normally but my start with automatic repair.



#14 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:07:09 AM

Posted 05 February 2017 - 01:16 PM

Please check the automatic repair log for reason why Windows wont boot.

Please execute following commands.

Sfc   /Scannow   /OFFBOOTDIR=C:\    /OFFWINDIR=C:\windows

Replace the C:\ drive letter with Windows installed partition drive letter.

Chkdsk  C:  /r

Replace the C:  drive letter with Windows installed partition drive letter.

 

Restart your computer.


Posted Image


#15 Sherif06

Sherif06
  • Topic Starter

  • Members
  • 12 posts
  • OFFLINE
  •  
  • Local time:10:09 PM

Posted 05 February 2017 - 07:16 PM

Hello,

I have ran the above commands and restart the computer. The computer starts with automatic repair again. Here is the pic of the message I received after the end of the Chkdsk command. Thanks.

Attached File  20170205_180253.jpg   104.6KB   0 downloads






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users