[SOLVED] Dell Optiplex won't boot into W10; don't know local Admin pass. FIX: I was able to change PW, went in recovery mode, did reset keeping settings&files

Hi,

So I put in a mechanical HD and installed a fresh copy of Win 10 just to be able to run Crucial Storage Exec on the P2, because CSE is Java based and won't run in a Win PE environment.

The results:

1700592621235.png

1700592647271.png

1700593513112.png

Are we satisfied this isn't a problem with the physical drive?

Yes, I am annoyed, because before all this it would put me into recovery mode and the only issue was I didn't know the Admin password.

Now I am in far worse shape because it is no longer doing that, and now it's saying device not available.

Had I just reset the Admin pass and done a recovery this would probably be over and done with.

But nooooooooooooooo....... everyone has me jumping through hoops with nothing to show for it.
 
Last edited:
Let me just be clear what I'm asking for.

I just want to be put back where I was when I started, namely, the PC prompts me to go into recovery mode. It's not even doing that now.

See, this is what happens when I'm "helped" by someone who doesn't understand the difference between a physical drive not having any free space because it's all assigned to partitions, and a logical drive / volume not having any free space because it's assigned to files and folders.

Just put me back where I was. And that would be before Message #48, when I started getting the new blue screen.

Please and Thank you.

Happy Thanksgiving.
 
Last edited:
So what's happening now is, on a cold start, you get this:

1700667686758.png
Then you hit F1 to go into recovery and you get this:

1700667779262.png

And on each F1 after that, you get this:

1700667812366.png

If I were a betting man, I'd say the BCD store was corrupted, and that would be around the time I was asked to edit it, prior to msg #48. I don't think it's hardware because as I've said ad nauseam chkdsk is fine, and now Crucial Storage Exec is fine too. But what do I know.

That's where things stand now.....

Thank you and Happy Thanksgiving.
 
Last edited:
Did you copy the c: partition as a backup?

In the recovery environment or safe mode with command prompt, launch these commands:
Code:
bcdedit
diskpart
List disk
select disk 0
List volume
List partition
Post their results here.
 
@xilolee
Code:
Microsoft Windows [Version 10.0.19041.3208]
(c) Microsoft Corporation. All rights reserved.

X:\Sources>bcdedit

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume4
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {bac62019-8676-11ee-a840-a040f199fcbc}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 10
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {bac62019-8676-11ee-a840-a040f199fcbc}
nx                      OptIn
safeboot                Network
bootmenupolicy          Standard

X:\Sources>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MININT-CJ9TQI1

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB      0 B        *
  Disk 1    Online           14 GB      0 B        *

DISKPART> sel disk 0

Disk 0 is now the selected disk.

DISKPART> list vol

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     F                       DVD-ROM         0 B  No Media
  Volume 1     C                NTFS   Partition    465 GB  Healthy
  Volume 2         Recovery     NTFS   Partition    529 MB  Healthy    Hidden
  Volume 3                      FAT32  Partition     99 MB  Healthy    Hidden
  Volume 4     D   WIN10PRO-22  NTFS   Removable     14 GB  Healthy
  Volume 5     E   UEFI_NTFS    FAT    Removable   1024 KB  Healthy

DISKPART> list part

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           529 MB  1024 KB
  Partition 2    System              99 MB   530 MB
  Partition 3    Reserved            16 MB   629 MB
  Partition 4    Primary            465 GB   645 MB

DISKPART> exit

Leaving DiskPart...

X:\Sources>
X:\Sources>
 
@xilolee
Code:
D:\dan>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MININT-CJ9TQI1

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          465 GB      0 B        *
  Disk 1    Online           14 GB      0 B        *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> select part 2

Partition 2 is now the selected partition.

DISKPART> detail part

Partition 2
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 555745280

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 3                      FAT32  Partition     99 MB  Healthy    Hidden

DISKPART> select part 4

Partition 4 is now the selected partition.

DISKPART> detail part

Partition 4
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 676331520

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1     C                NTFS   Partition    465 GB  Healthy

DISKPART> exit

Leaving DiskPart...

D:\dan>
D:\dan>

Mille grazie
 
Code:
D:\dan>bcdedit /set {bootmgr} device partition=\Device\HarddiskVolume2
An error has occurred setting the element data.
The request is not supported.
 
Code:
D:\dan>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MININT-CJ9TQI1

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> Select partition 2

Partition 2 is now the selected partition.

DISKPART> Assign letter=Z

DiskPart successfully assigned the drive letter or mount point.

DISKPART> exit

Leaving DiskPart...

D:\dan>Bcdedit /set {bootmgr} device partition=Z:
The operation completed successfully.

D:\dan>

Unfortunately, it's still doing the same thing as Msg #83
Dell Optiplex won't boot into Windows 10; don't know local Admin pass
 
If in the recovery environment Windows is still in c:, run these commands.
Otherwise change the letter accordingly:
Code:
diskpart
select disk 0
Select partition 2
Assign letter=Z
Exit
bcdboot c:\windows /s Z: /f UEFI /v
Post the result before the reboot.
 
Code:
Microsoft Windows [Version 10.0.19041.3208]
(c) Microsoft Corporation. All rights reserved.

X:\Sources>notepad

X:\Sources>diskpart

Microsoft DiskPart version 10.0.19041.964

Copyright (C) Microsoft Corporation.
On computer: MININT-0R4M2KA

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> select partition 2

Partition 2 is now the selected partition.

DISKPART> Assign letter=Z

DiskPart successfully assigned the drive letter or mount point.

DISKPART> exit

Leaving DiskPart...

X:\Sources>bcdboot c:\windows /s Z: /f UEFI /v
BFSVC: ServiceBootFiles MuiOnly:n Res:y Fonts:y BootMgrOvw:n BootStatOvw:n DbgTrn:y SuspendBDE:n
BFSVC: Using source OS version a00004a610001
BFSVC: Copying boot files CopyBootManager(No) c:\windows\boot\EFI -> \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot
BFSVC: Creating Recovery directory.
BFSVC: Logging boot file servicing to bootstat log \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot\BOOTSTAT.DAT.

BFSVC: Copying font files from c:\windows\boot\Fonts to \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot\Fonts...
BFSVC: Copying resource files from c:\windows\boot\Resources to \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot\Resources...
BFSVC: Servicing debugger files
BFSVC: List of debugger files is empty
BFSVC: System partition is not in a space
BFSVC: BfsInitializeBcdStore flags(0x0000021c) RetainElementData:n DelExistinObject:n
BFSVC: VolumePathName for c:\windows is c:\
BFSVC: Opening template from \Device\HarddiskVolume4\windows\System32\config\BCD-Template.
BFSVC: Opening store from \Device\HarddiskVolume2\EFI\Microsoft\Boot\BCD
BFSVC: Creating General objects.
BFSVC: Creating Resume object.
BFSVC: Creating MemTest object.
BFSVC: Creating OsLoader object.
BFSVC: OsLoader identifier: {ebd07ed8-8981-11ee-a304-b300c98ce24d}
BFSVC: Removing duplicate entries.
BFSVC: Removing duplicate object {bac6201a-8676-11ee-a840-a040f199fcbc}
BFSVC: Create BOOTMGR object RetainBootDefault:n
BFSVC: Setting {default} to {ebd07ed8-8981-11ee-a304-b300c98ce24d}
BFSVC: Cleaning up debugger settings.
BFSVC: Opening recovery store from \Device\HarddiskVolume2\EFI\Microsoft\Recovery\BCD
BFSVC: Creating General objects.
BFSVC: Create BOOTMGR object RetainBootDefault:y
BFSVC: Setting {default} to {b270c377-9fb2-11eb-91fc-8e50a3142ff7}
Boot files successfully created.

X:\Sources>


Awaiting further instructions ......................
 
No, the one from 0xc0000001, the failure to go into recovery mode.

Oh wait, that isn't a true blue (!) screen is it, with a memory dump. That's just an error message? Jeepers.

Any other files you need?

What's a 0xc0000001 trying to tell us?
 
Save sequence as above, 0xc000021a, then failure to go into recovery 0xc0000001, then failure to go into recovery again with 0xc000000e
 
Back
Top