Win 10 pro desktop will not boot… BSOD

Topic

New Reply

Need help please. My hp desktop running win 10 pro will not boot. It just keeps saying that it cannot start and keeps going into diagnostic mode. None of the onscreen options iwork .

I have discovered (using command prompt mode) that all my drive letters have changed for some reason.  I list the volume  of Hdd below

Sys reserved  is now  “C”    —  should be hidden
My PC disk is now  “D’  —  should be”C”
DVD drive1 is now “G”  — should be “D”

As I cannot get into “C drive  I cannot use safe mode for sys restore. To try and see what I can do

I have looked on various forums and they all say use safe mode…. cannot boot onto “C” drive so am stuck

DVD drive2 is now H’   — should be “E”
My partition 1 is now”F”

Any suggestions please

Reset PC, System Restore, Refresh keep restarting my PC  and it

Reply | Quote

Replies

David Hern wrote:

It just keeps saying that it cannot start and keeps going into diagnostic mode.

Do you have the exact wording of the message that you’re getting when you try to boot the PC? That may help in narrowing down the problem.

In my experience, it’s not unusual for drive letters to be different when you’re in some kind of recovery environment than when you’re in normal Windows. (Of course, that means that extra care needs to be taken when issuing commands in that environment.)

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

Thanks for your replies. guys, they are most welcome

I am using  the Nov 19 version 1909.

I do not know what made this fault. I just switched on my PC about a week ago and got the message that windows couuld not start and it then went into diagnostic repair mode..

I tried all the options… ontinue, system restore etc they just returned me to the same point, your PC  cannot start.

As I mentioned earlier, I did manage to get ino command prompt mode and discoverd that all my drive letters have changed. Diskpart volume shows My windows drive is now D , my sys reserved partition is now drive  C,  my photo partition is now drive E and my music partition is drive F. My 2 DVD’s are now drives G and H.

I have not yet triued to run the option in RE to load an ISO version of Win 10 from media creation tool… will this work  or will id damage all my files?

Usinga USB to SATA adapter I  can get easily inro my HDD and read my windows disk, can I reset drive letters this way please.

If so Can someone help with a step by step guide.  thanks.

 

Reply | Quote

Do not reset your drive letters, that is not the issue.
Your drive may be broken / on its way out. Or your hardware. It may have been power related or a virus etc, etc…

Make a backup and then rebuild – as I said. Then it doesn’t matter what the issue is as your data is safe.

cheers, Paul

Reply | Quote

What version of Win10 are you running 1809, 1903, 1909?
Did the computer just update?
What anti-virus program are you using?

Reply | Quote

Hi

Am using 1909 version

No did not up datethat I know of, it just occured when I switched PC on

I little history  (but I do not believe it is connected) . My PC was originally supplied with Windows 7pro.  I upgradedto Win 10 in Nov 19 as I had to bite the bullet and make the jump eventually

McAfee Livesafe

Please see other replyies also

Thanks

Reply | Quote

Make a backup of the machine to an external USB disk by booting from the backup software boot USB, if possible.

Re-install Windows and pick up any files you need from the backup.

cheers, Paul

Reply | Quote

Yes, you can use DISKPART to change the drive letters.  It has to be invoked from an elevated Command Prompt.

First create a full drive image to an external drive.  Then get back into an elevated Command Prompt and open DISKPART.  To remove the drive letter from your system reserved partition, first use the command

list volume

and hit Enter.

You should be able to tell from that listing which is your system reserved volume.  Use the command

select volume x  (where x is the volume number DISKPART shows for you system reserved volume)

and hit Enter.

The system reserved volume now has focus.  In the OP you said it had the drive letter C.  Next use the command

remove letter=c

and hit Enter.

You said “My PC disk is now “D’ — should be”C”.  Use the “list volume” command again, note the number of the volume that should be C, then use the “select volume” command again to select that number.

Then use the “remove letter=d” command (if it still is shown as D; otherwise, use whatever letter is shown, and remove it using that command).  Next you’ll need to assign the correct drive letter.  Use the command

assign letter=c

and hit Enter.

Now use the “list volume” command to see if things look more like they should.  Continue in this fashion until the drive letters look like they should, then try a restart and see if it boots into Windows.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Hi bbearren

Thanks for your assistance,

Did as you suggested using diskpart and remove/assign and all went successfully.  Checked with list volume… all good.

However  on restart  no change,  PC went into auto repair  again , all same as original problem.

Checked in command prompt and all my changes were gone, it was back to all the wrong drive letters AGAIN!

Did a need to save all these changes before typing “exit”  in command prompt?    If so could you tell me how?

Thanks for you help

David

Reply | Quote

Drive letter assignments are arbitrary.
If you boot from Windows OS, your OS drive will be C: and the DVD drive will be D: because they are assigned those letters in the Windows OS.
If you boot from another device, the Windows OS drive may/will have a different drive letter depending on the order devices are mounted.

See #2260090.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Hi again.

As I mentioned earlier, my windows 10 is an upgrade  version from the Microsoft media centre.

If I do a reinstall of win 10 from an ISO image, how will this then obtain the valid product licence key?

My old win 7pro has now gone (I assume).

Will I have to reinstall Win 7 first   before doing the win10 upgrade version from MSN  media creation centre?

Regards David

Reply | Quote

If you had an activated copy of Win10 on the PC previously, the PC should have a digital entitlement (license) recorded in the MS database associated with that machine (whether you had an MS account or just a Local account).

The PC should automatically activate when you reinstall Win10 from scratch.

Reply | Quote

David Hern wrote:

As I mentioned earlier, I did manage to get ino command prompt mode and discoverd that all my drive letters have changed.

David, I would suggest that you try this: get back into that command prompt mode, navigate to your Windows drive, and then type the following commands to reconstruct your master boot record:

bootrec.exe /fixmbr

bootrec.exe /fixboot

The cautious way to proceed would be to reboot the computer after the first step (fixmbr) and before trying the second step (fixboot). If you can boot into Windows normally after the first one, then you don’t need the second one.

Let us know if this helps.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

Hi Cybertooth

Thanks for your advice. Did try your suggestion regarding resetting boot rec

but no change … still as original problem. Again do I need to save changes before exiting command prompt, if so how?

Thanks daDave

Reply | Quote

Cybertooth

Sorry forgot to mention that when I tried to enter the second command…  /fixboot  the reply was “access is denied”  for some reason.

David

Reply | Quote

The drive letter issue is irrelevant. On BIOS/MBR systems you will always see a different drive letter assignment in recovery environments because the System Reserved partition is first on the disk, and therefore assigned as C.

Changing the drive letters in the recovery session only changes them in that session, which is loaded to a RAM disk. So the changes are lost if you reboot.

Reply | Quote

Get back into Command Prompt and run this command

bootrec /rebuildbcd

After that command completes, reboot the PC and see if it boots into Windows.  If that doesn’t fix it, there are a couple more options, as well.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Have just tried your latest suggestion of bootrec  / rebuild

This is the reply..  “successfully scanned windows applications, Total identified windows installations  0,   The operation completed successfully”

Is this correct?

 

Reply | Quote

[bbearren]

It is correct in that the tool did not find any Windows installations that are not included in the BCD store.  That means your Windows installation is included in the BCD store, but something is keeping it from starting correctly.

Did you try to restart?

If Windows doesn’t boot, what is the message that you’re seeing?

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

• This reply was modified 5 years ago by bbearren.

Reply | Quote

Yes tried a restart and just the same.

The messages I get on start up are…

1. Your PC ran into  a problem, it needs to restart. Collecting informatiom

Next screen .  Preparing automatic repair.

Next  screen.  Diagnosing your PC.

Next screen.   Your PC did nt start correctly and it then gives me option to trouble shoot

Reply | Quote

Thanks.  You’re getting booted into the Windows Recovery Environment (WinRE) which is, for all intents and purposes, still part of the Windows that won’t boot.

In order to effect repairs, you need to boot your installation media (in other words, get completely separated from the Windows installation that won’t boot), skip the “Install now” down to “Repair your computer” and click that.

Go to “Troubleshoot” > “Advanced options” > “Command Prompt” and click on “Command Prompt”.  The Command Prompt will be X:\>

Once you’re in the Command window, run this command again

bootrec /rebuildbcd

You’ll likely get the same result as before, “successfully scanned windows applications, Total identified windows installations 0, The operation completed successfully”, since in all likelihood the BCD store is munged.  Next run this command

bcdedit /export d:\bcdbackup

You should get, “The operation completed successfully”.  If WinRE has picked up your optical drive as “D:”, that command will fail; just use a different letter, but not C:, as I understood that your system reserved partition is first on the disk, and we don’t want to save there.  Let me know how that goes, and then we’ll proceed.

 

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Yes I am, and was already in command prompt via troubleshoot > advanced options. However my start point says  x:\WINDOWS\system32

I then use CD..  twice to return to just the x: prompt.

Have done the export x: \BBC bcbackup to D .  Shows as successful

If you recall , the d drive is the drive that volume shows as my windows drive.

Reply | Quote

David Hern wrote:

If you recall , the d drive is the drive that volume shows as my windows drive.

Yes, that’s fine, that’s why I wanted you to use it.  The file will do no harm there, and will be accessible if necessary (but probably won’t be).

Now try this command

ren d:\boot\bcd bcd.old

If that is not successful (access denied), try this command

attrib d:\boot\bcd -h -r -s

If that is successful, try

ren d:\boot\bcd bcd.old

again.  If that succeeds, then try

bootrec /rebuildbcd

one more time.  Let me know how all that goes, and then we can proceed.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

The first command  rename (ren d:) did not work.

Cmd reply stated ” the system cannot find the file specified”

The se ond command  (attrib d:) also did not work

Cmd reply stated path not found.  – d:\boot

I did a dir on drive D and there is in fact a file called bcdbackup,  but no reference to boot

Can I ask if it would be less hassle if I just did a reinstall of win 10 assuming I can validate the product key .

Reply | Quote

[Cybertooth]

Depending on how long you’ve been using that Windows 10 installation, it could be a huge hassle to reinstall Windows and then reinstall (entering license keys, passwords, etc.) all the programs that you have on it.

At this stage I would keep trying along @bbearren’s lines for a little longer. How about getting back into that recovery environment with the command prompt, but trying to locate that bcd file prior to entering bbearren’s commands. For example:

dir d:

and then see in the resulting list if you can find the bcd file, or perhaps the \boot folder in which case you could navigate to the folder and see if the bcd file is there:

cd boot

dir

Once you establish where the bcd file is, you can then enter that path to rename it the way bbearren suggested.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

• This reply was modified 5 years ago by Cybertooth.

Reply | Quote

Thanks for reply.  I really do not want to do the reinstall of win 10  either.

I wanted to  ask bbearren for his opinion as he has the knowledge and expertise to make an informed decision. He  has also spent some considerable time  helping  me.

Reply | Quote

Good Morning, have you seen my last message and that of cybertooth ?.

As I mentioned there is a file called bedbackup in drive d but no mention of ” boot.  Also  on doing a “cd boot” the reply is  “the system cannot find the path  specified”

Is that correct?

Reply | Quote

A little more…

In “d” drive I did the following… cd windows and then c d boot and did a dir.

There are  directories and one file called “bootdebuggerfiles.ini”

The directories are  DVD, EFI, Fonts, Misc, PCAT and Resources

Is this of any help?

Reply | Quote

Yes, you can reinstall Windows. As long as you have a legit copy of Windows 10 it will automatically activate.

See here: https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install-winpc/how-to-perform-a-repair-upgrade-using-the-windows/35160fbe-9352-4e70-9887-f40096ec3085

My 1st, #1, AllStar advice? Have a valid backup image of your drives.

Macrium Free

Aomie Backupper

Acronis True Image (not free but very good)

Reply | Quote

David Hern wrote:

Good Morning, have you seen my last message and that of cybertooth ?.

As I mentioned there is a file called bedbackup in drive d but no mention of ” boot.  Also  on doing a “cd boot” the reply is  “the system cannot find the path  specified”

Is that correct?

Hi David,

I thought that name looked familiar.  If I remember correctly, you’re in South Africa?

Yes, I’ve read your last posts, but before today I had (mistakenly) assumed that you were going to do a re-install.  And sure, I’m more than willing to work through this if you like.

Since you did find d:bcdbackup, unless you have run the command

bcdedit /export c:bcdbackup

sometime in the past (when Windows is booting and that command is run, “C:” is the logical target), we can assume bcdedit.exe can indeed find the BCD store, so let’s see what it looks like.

Booting your installation media as before, get back into Command Prompt and run this command

bcdedit

and hit Enter.  You may get an “access denied” message, or you may get the BCD store, something like this:

We’re particularly interested in Windows Boot Manager device, Windows Boot Manager path, as well as Windows Boot Loader device and path.  The rest is not pertinent to what we’re currently trying to do at the moment.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Hi, I think your mixing me up with another, I live in South Wales in UK , city called Cardiff.

Sorry I was only asking about doing a reinstall as I was taking up lots of your time . I would prefer to fix it and am very happy that you are helping me.

With reference to bcdedit /export c:bcdbackup, we actually did do it yesterday. It is sitting in drive d.

I have run bcd edit and I get a screen very similar to your one.

What NEXT?

Reply | Quote

David Hern wrote:

I have run bcd edit and I get a screen very similar to your one. What NEXT?

Under Windows Boot Manager mine lists
identifier                       {bootmgr}
device                             partition=\Device\HarddiskVolume19
path                                \EFI\Microsoft\Boot\bootmgfw.efi

and under Windows Boot Loader it lists
identifier                        {current}
device                              partition=C:
path                                 \Windows\system32\winload.efi

What are those values in your listing under those headers?  This will help me figure out where the BCD store is located.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Boot manager..

Identifier               (bootmgr)

Device                   partition=c:

There is no “Path” listed in boot manager, it is missing

 

 

Boot Loader..

Identifier           (default)

Device                 partition=D:

Path                     \windows\system32\winload.exe

 

Reply | Quote

Sorry for the long delay, I had to run an errand.

We know that your system drive (which is labeled D) does not have a D:\Boot folder.  The Boot folder in the Windows folder is not used for booting, so that’s not going to help.

From your installation media Command Prompt type D: and Enter to change to the D: drive.  Then try this command

ren bcd bcd.old

Let me know what you get.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

No  problem,thanks for telling me,

Entered the command and reply is..

‘The system cannot find the file specified”

Reply | Quote

David Hern wrote:

‘The system cannot find the file specified”

I’m working from the assumption that you’re booting your installation media and getting into Command Prompt from there.

Open DISKPART, and assign a drive letter to your system reserved partition.

Exit DISKPART and change to that drive letter in Command Prompt, and run a

dir

command.  Let me know the results.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Hi

Opened diskpart and assigned sys resv (C) to letter “w”

Exited disk part and changed to drive W,.

It did appear to change to new drive but  command prompt is showing  D:\>

When I do a “dir” it is showing the contents of directory of D

 

<!–more–>

Reply | Quote

Run DISKPART again and see if the System Reserved partition is still drive letter C.  If so, exit DISKPART and run a dir command on C.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Did run diskpart again and volume showed the sys resv hac indeed changed from letter  C to letter  w

Sorry should have mentioned that in last post.

Reply | Quote

David Hern wrote:

Did run diskpart again and volume showed the sys resv hac indeed changed from letter C to letter w

If you haven’t already, change your Command Prompt to W (type w and then Enter)

Once the Command Prompt is rooted in W: run a dir command.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

David Hern wrote:

Path                     \windows\system32\winload.exe

This tells us that your machine is booting in MBR mode. Is the machine old or new?
Do you have a small (100MB) partition called “EFI system”?

cheers, Paul

Reply | Quote

Hi,  my machine is hp7800 quad core which originally had win 7pro installed. So it is quite old.

Cannot fine any partition or reference to  EFI system  on drive D

Cheers

Reply | Quote

Paul T wrote:

Do you have a small (100MB) partition called “EFI system”?

In my experience OEM Windows 7 is always BIOS/MBR; I’ve never encountered a UEFI/GPT OEM Windows 7 installation.  Windows 7 is quite capable of running on UEFI/GPT, I’ve converted MBR to GPT myself.

However, an upgrade to Windows 10 from Windows 7 has no need for an EFI partition (only necessary to boot from a GPT disk), and no EFI partition is created in the upgrade process.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

You definitely have an MBR system.

The fact that it boots to disk at all shows the boot information is fine, but your OS (Windows) is not happy. The easiest fix is always re-install saving existing data. Anything else requires we can work out what is wrong and fix those bits manually – we’ve not managed it so far.

cheers, Paul

Reply | Quote

[Cybertooth]

David, since you don’t have a \boot directory and you can’t find the bcd, the bcd might be in your root directory. You may want to try Step 7 in this tutorial to make the bcd visible, then proceed with @bbearren’s instructions above for renaming the bcd file. (He may then ask you to perform additional commands similar to those given in Steps 9 and 10 on that tutorial.) Modified for your case, the command would be:

attrib bcd -h -r -s

Just make sure to enter the correct drive letter (instead of c:). I think you’ve reported that it’s drive d: in your case.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

• This reply was modified 5 years ago by Cybertooth.
• This reply was modified 5 years ago by Cybertooth.

Reply | Quote

Cybertooth wrote:

you might want to try Step 7 in this tutorial

We’re past that already.  Bootrec /rebuild bcd won’t work if there is an existing bcd.  In order for that command to work, the bcd must first be deleted or renamed (rename is usually the preferred option).  That’s what I’m working toward with David now.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Have just managed to read dir of sys resv “W” it says…

Volume in drive W is sys reserved

Volume serial number is 9021-E13A

Directory of W:\

File not found

It is now sitting with the “W” prompt

 

 

Reply | Quote

David Hern wrote:

Directory of W:\ File not found

Get back to the installation media RE by typing X and hit enter.  Let me know when you’re there.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

That is in fact how I did get back to the “X” letter.

I actually have to exit and then come back in just typing the letter X  does not work.

Can I please ask if there is a way to easily see when you have replied   and would it be possible to move or something similar

At the moment I am constantly scanning where to find your latest reply is in this post log

Reply | Quote

But the problem is that the bcd can’t be renamed if it’s hidden. (This would also account for the inability to find it in the recovery environment.) Therefore the attributes need to be changed first.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

David, I agree that the thread is getting congested.  To make it easier for you to find my replies, I won’t “reply” to you directly, I’ll just post at the bottom of the thread.  You can find me there easily enough.  Try this command

bootrec /scanos

and let me know the results.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Did bootrec /scanos

Reply.   Successfully scanned windows installations

Total identified windows installation:  0

The operation completed  successfully

 

 

Reply | Quote

Just to mention  I did the boot rec from the “W” prompt

Reply | Quote

If this command works, a box will open asking for your administrator password, and a second, Administrator Command Prompt will open.  Try

powershell -command “start-process cmd -verb runas”

And let me know the results.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Reply…..  is not recognized as an internal  or external command, operable program or batch  file.

Reply | Quote

Change your Command Prompt to D:  The prompt should read “D:\Windows\system32>”.

Next type

cmd

and hit Enter.  That should just give you another line with the same prompt, but you’ll be running the Command Prompt from D: drive instead of X:.  If that goes as I’ve anticipated, try

powershell -command “start-process cmd -verb runas”

again and let me know the results.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Again not recognized as valid command

it may be that I am not putting any spaces between text except verb runas although I have tried variations  but they give same result.

Reply | Quote

The syntax is important.

powershell -command “start-process cmd -verb runas”

That’s

powershellspace-commandspace“start-processspacecmdspace-verbspacerunas”

Can you give that another go with the correct syntax and let me know how it goes?

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

I an in  D:\windows\system32>

Reply… “powershell ” is not a recognized as an internalor external command etc.

I did follow the syntax and did it 3 times all with the same results.

I would say it is very difficult to see the spaces on my small smamsung tablet

Reply | Quote

David Hern wrote:

I an in D:\windows\system32>

Try

cd windowspowershell

and hit Enter.  If your prompt changes to D:\Windows\System32\WindowsPowerShell> then try this command

powershell

and Enter.  If your prompt changes to

PS D:\Windows\System32\WindowsPowerShell> then try the command

powershell -command “start-process cmd -verb runas”

again, mindful of the spaces.  Let me know the results.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

The path did  change to d:\windows\system32\windowspowershell as you said but when I then entered the command powershell, I had the same. message … powershell is not  recognized as …….

Reply | Quote

[bbearren]

That’s looking better.  The executable is in a sub-directory.  Try

cd v1.0

and hit Enter.  If that worked correctly, try

powershell

and Enter. If your prompt changes to

PS D:\Windows\System32\WindowsPowerShell> then try the command

powershell -command “start-process cmd -verb runas”

again, mindful of the spaces. Let me know the results.

 

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

• This reply was modified 5 years ago by bbearren. Reason: context

Reply | Quote

No still not there,

I now have..D:\windows\system 32\windowspowershell\v1.0

When I then type powershell it just comes back with the same as above

. It ignores the word “powershell ”

 

Reply | Quote

• No, still the same. However I have noticed that I do not have the letters “PS”  in front of  the command line. Mine just starts with D:\

 

Reply | Quote

Run a dir on D:\windows\system 32\windowspowershell\v1.0

Is powershell.exe in that directory?

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Yes  there is  in fact there are these as well

Powershell.exe

Powershell.exe.config

Powershellcore.format.ps1xml

Powershelltrace.format.ps1xml

Powershell_ise.exe

Powershell_ise.exe.config

So why will not load , do I need  add  .exe ?

 

Reply | Quote

David Hern wrote:

So why will not load , do I need add .exe ?

Typically that isn’t necessary, but by all means, mindful of the spaces, try

powershell.exe -command “start-process cmd -verb runas”

and hit Enter.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

David Hern wrote:

No, still the same. However I have noticed that I do not have the letters “PS” in front of the command line. Mine just starts with D:\

Try just

powershell.exe

without any switches, and let me know what that does.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Tried but Nothing… still the same

Reply | Quote

Go back to D: drive for your prompt, then do a dir command and let me know if bootmgr is listed in the files.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

In D: drive and  bootmgr is not showing or listed in the dir, also checked in windows dir … nothing there <!–more–><!–more–>

Reply | Quote

I shall try tomorrow if ok with you. It is now 23:15 here.

Goodnight

Reply | Quote

Goodnight

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Change your Command Prompt back to W:  Then, being mindful of the spaces, run this command

attrib -s -h -r \boot

If that completes successfully, run a dir command, and let me know the results.

 

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

Reply | Quote

Hi, hope you had a good weekend. I do not have my PC at this time., I t is now  with a colleague  of a friend who is (I am told) like yourself is very good with computers. I do hope you’re ok about that.

I really do appreciate all your assistance, time and patience  helping me to fix this boot / start up problem. I just felt it was robbing us both of so much time.

Onc1e again … thank you so much. I shall contact you when I have it back and hopefully  working once more.

Regards David

Reply | Quote