Main Forum > General Computer Support

windows 10 wont boot

(1/3) > >>

heptigb:
I have a windows 10 pc that wont boot, when started it attempts to run a repair on it self and that fails and it wants a  windows cd which I dont have(machine purchased ith os installed no media). I bought a cd called fix it now that boots the computer in widows 8 and contains tweaking application ver 3.7 so apparently older than what is current. In attempting to set the log path  the cd creates a drive and wants to set the path to the cd so I set it to my hard drive so it has a writable path. The OS is on the d: drive does that path get set somewhere else or does the log path tell it where the os is located?

Boggin:
If you have access to another machine then you can create Win 10 install media after reading the instructions at https://www.microsoft.com/en-gb/software-download/windows10

What was the most recent thing prior to the machine not booting up - had you installed anything ?

When you boot up with the install media - an USB is best - navigate to the Install screen and click on Repair your computer then click on Troubleshoot and select Start-up Repair to see what that reports.

If it reports it is unable to repair the machine, click on Advanced/Troubleshoot and select Command Prompt and enter these cmds -

bcdedit |find "osdevice"

For clarity that is a Pipe symbol before find and is the uppercase of \

Using your partition letter instead of the x I have exampled, enter chkdsk x: /r

Check to see if it reports any bad sectors on the HDD.

If that comes back clean then again using your partition letter instead of the X I have exampled, enter this cmd -

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

Note the space before each /

If it does report bad sectors then you should back up the drive ASAP.

This article will help with that but you will need access to another machine to create the Linux USB.

https://www.howtogeek.com/howto/31804/the-10-cleverest-ways-to-use-linux-to-fix-your-windows-pc/

If the chkdsk comes back clean, then you could try the System Restore option, although I'm wary of restore points but they may work for you.

heptigb:
Tom

Thanks for your help I ran check disk and it found some errors so I let that complete I, then attempted to run the commands for sfc, but it appears there is an error in syntax as it gives a syntax structure screen, see attacments, thanks very much for your help.

Bill

Boggin:
The syntax error that you have created is that you haven't put a space between the backward and forward slashes at offbootdir=d:\ /offwindir=d:\Windows

As you can see from my example below, I've replicated the syntax error that you have by booting up with a Win 10 install USB and entered the cmd without that space and got the same cmd window read out as you.

sfc /scannow /offbootdir=d:\/ offwindir=d:\Windows

Try the cmd again with that space between the two slashes.

However, the fact that the chkdsk has repaired the file structure may have been sufficient but I'd still go ahead with that sfc /scannow cmd to see what it reports.

heptigb:
Currently because the machine wont boot I using a utility that boots it from the cd its creating drives that are ram drives I think, consequently the mappins look like the attachment The d drive contains the windows 10 files and apparently the x: dive is created by the cd as a place to boot the machine when it loads from the cd, perhaps some modification of the path is need to tell to ignore x:?  Thanks aging for assistance

Navigation

[0] Message Index

[#] Next page