Windows10 update damaged something, attempting repair, some advise adv

topgundcp said:

I think your ESP partition is messed up badly so let's try to re-create it. We will delete the partition 1 (ESP) then re-create EFI Partition and BCD.
Please take note on all spaces. A quick way is to copy and paste what I have below into the command windows.
Admin command, type:

diskpart
select disk 0
select par 1
delete par override
create par efi
format fs=fat32 quick
exit
mountvol U: /s
bcdboot c:\windows /s U: /f UEFI
mountvol U: /d

Reboot the PC

It was successfully doing everything right up to:
Mountvol U: /s

There it again says:
The parameter is incorrect

According to this link it could require a different command but I am not sure what they mean by "n" if that's letter E or volume 2, I don't want to screw it up by typing the wrong thing. And I'm not sure if it's correct to my machine?

What the link says below:

You Cannot Access an EFI System Partition with the Mountvol Utility in a WinPE Environment

Symptoms

If you use the Mountvol utility (Mountvol.exe) in a Windows Preinstall Environment (WinPE) on either a Windows XP-based or Windows Server 2003-based computer, you cannot gain access to the Extensible Firmware Interface (EFI) system partition by using the mountvol /s command. For example, if you try to use the mountvol x: /s command, you may receive the following error message:
The system cannot find the file specified.

Cause

This behavior occurs because the Mountvol utility is not supported in WinPE environments.

Resolution

To work around this behavior, use the Diskpart utility (Dispart.exe) instead of the Mountvol tool. To use the Diskpart utility:
Click Start, click Run, type diskpart in the Open box, and then click OK.
When the Diskpart utility starts, type select disk n at the prompt (where
n is number for the mapped ESP disk), and then press ENTER.
Type select partition
n at the prompt (where
n is number for the mapped ESP partition), and then press ENTER.
Type assign letter=x at the prompt (where x is the drive letter that you want to assign), and then press ENTER.
After you follow these steps, you can access an EFI system partition by using the drive letter that you assign to the partition with the Diskpart utility.

Status

This behavior is by design.

***

Alright, so I will arrange to get a disc copied from that link of windows10 to use as a new recovery disc, and then I will return to this thread.

Thank you for your help and patience thus far, I will return soon.

Okay so I've been trying and trying and trying to get the windows10 from that link to follow through so I can make the ISO until I'm losing my cool and every time it won't let me - citing that some vague problem but without offering any kind of solution - and Microsoft responds with a myriad of replies (to others who also get the same error and problems message) and none of their worthless replies are any good.

I hate windows 10 and I hate Microsoft. This is their fault and their doing.

I hope that a worldwide class action lawsuit begins for people who have had their computers and files damaged by windows10 and Microsoft, on that I would join in a second.

Why can't we hold Microsoft accountable for killing computers and forcing unwanted software?

Why is nothing simple and straightforward with this company?

I am so mad as hell

I am going to try again with getting hold of the windows10 disc from the link (would a USB be equal?), I am going to try to work through the problems of just getting the link on disc or USB.

I will return with a help request in the near future if/when I can work through the trash that is Microsoft.

Two questions in the meantime please.

1. Does it make a difference whether I (hopefully) get the windows10 link on DISC or USB? Because if I am using some computers to access that link they don't have optical drives.

2. Is it possible to get /make copies of the files off the hard drive of the damaged computer?

topgundcp said:

You are talking about WinXP and Win Server 2003. Some of the info from the internet is pretty out of date.

EDIT: Here's the screen shot. I booted the Windows Installation which is a WinPE:


Something is not correct with your Recovery disk. Perhaps, you might want to download: Windows 10, boot up then try again with Command prompt.
Download Windows 10

Hello again, I hope that you are still around and interested in helping me and those who may read this with the same problem, to find the solution.

UPDATE.

So I now have a friend who used their computer to download the latest version of Windows10, I have it on USB stick and have set the laptop to have the USB as the priority boot device.

I have gotten back to the command prompt area of the recovery USB stick and I have done exactly as you describe in your reply.

I have unfortunately had exactly the same stopping-point:

Mountvol U: /s
(the following message again)
The parameter is incorrect.



Please advise,
thank you

AlphaUMi said:

About the mountvol command, I recently discovered that the parameter must be uppercase. So if you typed:

mountvol U: /d --> not correct
mountvol U: /D --> correct.

That is useful to know, I have tried with uppercase and lowercase and the result is the same

"The parameter is incorrect"


I don't know what to do at this point.


Upon doing dskchk I get the following information:


The type of file system is NTFS

The volume is in use by another process

Volume label is Boot

WARNING! /F parameter is not specified.

Running CHKDSK in read-only mode.

Read-only chkdsk found bad on-disk uppercase table - using system table.


Stage 3:
Errors detected in the uppercase file.

Windows has checked the file system and found problems.
Run CHKDSK with the the /F (fix) option to correct these.


Failed to transfer logged messages to the event log with status 50


-----------

Now, I have typed

CHKDSK /F

And the reply is:

The type of file system is NTFS.
Cannot lock current drive.
Windows cannot run disk checking on this volume because it is write protected.

Additional information

Alright, so additional information is that I have also done:


Chkdsk C: /f /r /x

It scanned stage 1 to stage 5 and said "windows has scanned the file system and found no problems. No further action is required."

But then it says once again:

" failed to transfer logged messages to the event log with status 50"

So somethings still wrong.

I then typed:

"Chkdsk C: /r /f /v"

And it says:

"Chkdsk cannot run because the volume is in use by another process. Chkdsk may run if this volume is dismounted first. ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID. Would you like to force a dismount on this volume? (Y/N) "

So at this point what do I do?
I don't really understand all of these terms