BSOD after a Visual Studio install Reboot Error 21a

axe0 · 17 Mar 2019

System has been trying to Attempt Repairs for more than a day now

Could you upload the log System Repair leaves behind please.

ravneetg · 17 Mar 2019

Hi axe0,

Can you point me to name of the log and steps on how to generate it again cleanly?

Thanks!

axe0 · 17 Mar 2019

When you're in the Advanced options, choose Startup Repair. It will fail, but it will generate a log of all actions taken and the result. It will also mention where this log is saved which is something like "\Windows\System32\LogFiles\Srt\SrtTrail.txt". After the startup repair failed, connect a USB stick, go back to the advanced options, go to command prompt and run the following commands

Code:

diskpart
list volume

This will tell you what letter is assigned to the USB stick, next enter the following commands

Code:

exit
copy "C:\Windows\System32\LogFiles\Srt\SrtTrail.txt" "X:\"

Please note that C: and X: are letters commonly seen in this kind of situations, of the letters are different for you please change the letters to the appropriate onces.

After the above is done, please upload the SrtTrail.txt file here.

ravneetg · 18 Mar 2019

SrtTrail.txt:
Attachment 227839

diskpart list volume output:

Code:

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    500 MB  Healthy
  Volume 1     H                NTFS   Partition    464 GB  Healthy <-- This is OS drive, I can see windows/user etc.
  Volume 2     D   System Rese  NTFS   Partition    100 MB  Healthy
  Volume 3     J                NTFS   Partition    111 GB  Healthy
  Volume 4     E   Data         NTFS   Partition    931 GB  Healthy
  Volume 5     F   ESD-USB      FAT32  Removable     14 GB  Healthy
  Volume 6     G   Seagate Bac  NTFS   Partition   1863 GB  Healthy
  Volume 7     I                NTFS   Partition    858 MB  Healthy    Hidden
  Volume 8     K                NTFS   Partition    450 MB  Healthy    Hidden

DISKPART> exit

Leaving DiskPart...

X:\Sources>copy h:\Windows\System32\LogFiles\Srt\SrtTrail.* g:\
h:\Windows\System32\LogFiles\Srt\SrtTrail.log
h:\Windows\System32\LogFiles\Srt\SrtTrail.txt
        2 file(s) copied.

axe0 · 19 Mar 2019

It looks like alongside the Visual Studio installation process, Windows Update was simultaneously installing something and it has trouble installing the update.

Code:

Test Performed: 
---------------------------
Name: Check for pending package install
Result: Completed successfully. Error code =  0x4
Time taken = 219 ms

0x4 = system cannot open file.

I'm not very familiar with this kind of issues, so I'll see what I can find to somehow revert the package. Right now I'm going home from school so I'll attend to this when I'm home.

ravneetg · 20 Mar 2019

No worries axe0, when you get time.

I tried reading other threads and ran a dism command to revertpending actions...but there I get a file permission error to write to. Will share the output soon.

FreeBooter · 20 Mar 2019

Please boot your computer with Windows Installation Media and from Windows Recovery Environment start the Command Prompt.

Please execute below command and reboot your computer to see issue resolves.

Code:

mkdir C:\scratch

DISM    /Image:C:\     /Cleanup-Image   /RevertPendingActions /ScratchDir:C:\Scratch

Please replace all of the partition letter C: with Windows installed partition letter. When computer boots into Windows Recovery Environment (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.

ravneetg · 20 Mar 2019

Thanks Freebooter.

I tried that again, created a g:\scratch, where g: is the os drive, I can see the Windows and USer folders etc.

On running DISM, I get a permission denied on G:\scratch\{GUID} where {GUID} is some guid.

I can upload the photo of the screen. Let me also try to create a file on that folder from notepad from Windows RE x:\sources prompt and see if I can save.

ravneetg · 20 Mar 2019

I tried again, this time bcdedit itself failed to return the information. I have seen this happen couple of times, but on diskpart list volume I can see the partition and the windows folders.

Below, I tried to create a 4 byte file on h:\scratch, and then run DISM on h:\

Code:

X:\Sources>dir h:\scratch
 Volume in drive H has no label.
 Volume Serial Number is D844-C6D6

 Directory of h:\scratch

03/20/2019  03:00 AM    <DIR>          .
03/20/2019  03:00 AM    <DIR>          ..
03/20/2019  03:00 AM                 4 test.txt
               1 File(s)              4 bytes
               2 Dir(s)  306,086,789,120 bytes free

X:\Sources>DISM /Image:H:\ /Cleanup-Image /RevertPendingActions /ScratchDir:h:\scratch

Deployment Image Servicing and Management tool
Version: 10.0.17763.1


Error: 605

An error occurred accessing the temporary folder h:\scratch\25420E00-9608-4F66-B540-2BCF0AF0F444.
Ensure that the path to the temporary folder exists and that you have Read/Write permissions on the folder.

The DISM log file can be found at X:\windows\Logs\DISM\dism.log

X:\Sources>bcdedit /enum
The boot configuration data store could not be opened.
The requested system device cannot be found.

FreeBooter · 20 Mar 2019

Please boot your computer with Windows Setup Media and from Windows Recovery Environment start the Command Prompt.

Please type below commands into Command Prompt and press Enter key.

Following commands will repair Master Boot Record (MBR), Boot Sector and BCD Store.

Code:

Bootrec /FixMbr

Bootrec  /FixBoot

Bootrec /scanos

Bootrec  /RebuildBcd