Error 0xC000009a when booting from flash drives

TraceyW · 30 Aug 2021

Hi
I have a problem I need to sort out as it involves my emergency flash drives. I have several flash drives for emergencies and three of them: Partition Assistant, Partition Wizard and ShadowMaker refuse to boot up and I stress that these are flash drives - currently Windows 10 boots up just fine.
When I try booting up using Partition Wizard I get nothing appearing on the monitor for a period of time (I've not timed it but I believe its several minutes) then the screen goes blue for a short while then the PC just switches off. With Partition Assistant and ShadowMaker, in very short order I get the error BlInitializeLibrary failed 0xC000009a but this is the only clue I have at present as to what may be happening.
I've searched the internet but haven't really come up with anything of any obvious use. However, what does seem to be common to all messages seeking help on this is Gigabyte mobos. I've just changed my mobo to an mATX Gigabyte B550M AORUS PRO and installed it in a new case - but those are the only two new items I've used. I DIDN'T do a fresh install but let Windows sort out what needed sorting out and so far Windows has been running fine although the CPU temps are jumping all over the place (but that is something for another day). Currently I'm primarily concerned with my emergency flash drives not running up as they should. Oh I've also tested the flash drives on my husbands PC and they run up perfectly.
Does anyone have any thoughts on what could stopping the flash drives running up? Any help would be most appreciated. Thanks
Tracey Woodmason
PS I should add that I've put this post in this section but whether its the right one or not I really don't know and apologise in advance if it causes anyone any inconvenience.
PPS I'm running 21H1.

Paul Black · 04 Sep 2021

Hello @TraceyW,

I have noticed that you have NOT had ANY replies, so I thought that I would try and help.

These are a good place to start diagnostics . . .

SFC and RestoreHealth

[1] Press the Win + X keys together > Command Prompt (Admin).
[2] Highlight ALL the commands below.

IMPORTANT:

It is recommended when running SFC that Fast Startup is turned OFF [ Turn it back ON when finished ] => How to Turn On or Off Fast Startup in Windows 10
If SFC finds any ERRORS that it can NOT repair, run SFC again upto 3 more times, Restarting after each to allow any pending actions to be implemented.
DISM will initially try and Repair ANY Corrupted or Missing files using the Component Store.
If this is NOT possible, DISM will use Windows Update. Therefore, Internet access is required.
If you are NOT connected to the Internet, you will receive a Error: 0x800f081f.

[3] Press the Ctrl + C keys together.
[4] Right-click inside the Administrator: Command Prompt Window > Paste.
[5] Press Enter.

Code:


sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow

When the above has finished processing . . .

[6] Right-click on the title bar of the Administrator: Command Prompt Window > Edit > Select All.
[7] Right-click on the title bar of the Administrator: Command Prompt Window again > Edit > Copy.

Paste the results into your post using the [CODE] tags . . .

[8] In your post, click the Hashtag icon #.
[9] Click INSIDE the [CODE]Here[CODE] tags and press the Ctrl + V keys together.

In your post it will look like this . . .

Code:


<<< Results here >>>

SFC Error Report

However, if there are STILL SFC ERRORS . . .

[1] Press the Win + X keys together > Command Prompt (Admin).
[2] Highlight the command below.

NOTE:

If you have a Relocated Desktop, then change the %UserProfile% part of the Command below to the actual path of the Relocated Desktop folder.

[3] Press the Ctrl + C keys together.
[4] Right-click inside the Administrator: Command Prompt Window > Paste.
[5] Press Enter.

Code:


findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log > "%UserProfile%\Desktop\SFC_Details.log"

This will create a SFC_Details.log file on the Desktop.

EITHER:

Copy & Paste the results into your post using the [CODE] tags . . .

[1] Open the SFC_Details.log file in Notepad.
[2] Press the Ctrl + A keys together.
[3] Press the Ctrl + C keys together.
[4] In your post, click the Hashtag icon #.
[5] Click INSIDE the [CODE]Here[CODE] tags and press the Ctrl + V keys together.

In your post it will look like this . . .

Code:


<<< Results Here >>>

OR:

UPLOAD the file => How to Upload and Post Screenshots and Files at Ten Forums.

I hope this helps.

TraceyW · 05 Sep 2021

Paul

Thanks for reply but I think I've made a decision on this in that the more I think about it the more I think its a problem with the mobo. Think about it - I can't boot up three of my emergency flash drives at all. One is Partition Wizard, a second is ShadowMaker and a third is Partition Assistant and the last two very quickly produce the error message in my post heading. To use them I have to reboot so I'm effectively starting from zero since I believe all the files needed are located on the flash drives.

Apart from this I HAVE run SFC and had a look at the CBS.log file myself. Now I don't know very much about this file but I put it into a text editor and did a search for 'corrupt' and the only ones that were found were associated with a WinHlp32 file from XP (I occasionally use Paradox written in the era of the days of XP so I need to have the XP WinHlp32 up and running). I've also used a couple of DISM commands which did replace my WinHlp32 file and I had to get the XP version back in.

What has occurred to me today is whether updating the BIOS may do any good. Its not a task I relish but if needs be I will do it. In the past it has solved problems I've had with a PC. So what do you think? Is it worth a try? I've already tried resetting my PC from scratch only to find out it was a waste of time but at least it helped me sort out ways of doing things that I was struggling with. Whatever, I'm now back to my original installation.

Again thanks for being the only one to reply so far (I'm not holding my breath for any more!). If you have any advice regarding updating the BIOS I'd be pleased to hear what you have to say.

Tracey

Paul Black · 05 Sep 2021

Hello @TraceyW,

TraceyW said:

I can't boot up three of my emergency flash drives at all. One is Partition Wizard, a second is ShadowMaker and a third is Partition Assistant and the last two very quickly produce the error message in my post heading. To use them I have to reboot so I'm effectively starting from zero since I believe all the files needed are located on the flash drives.

A couple of suggestions for this.

[1] You could perform a Disk Cleanup - Extended . . .

> How to Open and Use Disk Cleanup in Windows 10

[2] This thread might be useful . . .

> How to make Windows Forget USB Device as if it had Never been Plugged in?

TraceyW said:

What has occurred to me today is whether updating the BIOS may do any good. Its not a task I relish but if needs be I will do it. In the past it has solved problems I've had with a PC. So what do you think? Is it worth a try? I've already tried resetting my PC from scratch only to find out it was a waste of time but at least it helped me sort out ways of doing things that I was struggling with. Whatever, I'm now back to my original installation.

I think that is an excellent idea. At least then, if it does NOT work, you can scratch that from the to do diagnostics list.

TraceyW said:

Again thanks for being the only one to reply so far (I'm not holding my breath for any more!).

You are VERY welcome.

TraceyW · 05 Sep 2021

Paul

Thanks once again for your prompt reply.

Finding out what doesn't work was referred to by someone I used to work with as "negative fault-finding" (yes, I worked in electronics). I think a very apt description. Further to this though I've been finding out how to do it but my mobo manual (as downloaded from Gigabyte) has no info on it. Anyway I'm all set now (hooray for YouTube!). I've just got to gather together the courage to go ahead and do it. As I said, not something I do for the sheer hell of doing it. I may well leave it till tomorrow. In the meantime though I could go through the cleanup process not that I've got any great hopes.

Tracey

Paul Black · 05 Sep 2021

Hello @TraceyW,

TraceyW said:

Finding out what doesn't work was referred to by someone I used to work with as "negative fault-finding" (yes, I worked in electronics). Anyway I'm all set now (hooray for YouTube!). I've just got to gather together the courage to go ahead and do it. As I said, not something I do for the sheer hell of doing it.

Yes, there is a fine line between how long is acceptable on the time that you spend on Troubleshooting, and whether or NOT it is best to Backup your DATA and perform a Clean Install.

An alternative LESS destructive method, is to perform an In-Place-Upgrade - Repair Install.

I hope it goes OK tomorrow as I assume that you have checked and there IS a BIOS update?

I hope this helps.

tomdsr · 05 Sep 2021

TraceyW said:

Paul

Thanks once again for your prompt reply.

Finding out what doesn't work was referred to by someone I used to work with as "negative fault-finding" (yes, I worked in electronics). I think a very apt description. Further to this though I've been finding out how to do it but my mobo manual (as downloaded from Gigabyte) has no info on it. Anyway I'm all set now (hooray for YouTube!). I've just got to gather together the courage to go ahead and do it. As I said, not something I do for the sheer hell of doing it. I may well leave it till tomorrow. In the meantime though I could go through the cleanup process not that I've got any great hopes.

Tracey

No one has asked, but how old are these flash drives?

TraceyW · 06 Sep 2021

Tomdsr

Thanks very much for your reply. I'm not really sure but maybe 4 to 5 years possibly six. I get what you may be thinking but to be sure the drives were still OK I fired up my husbands PC with them and all was OK. No, I think I've got a bum mobo. I have now updated the BIOS but it hasn't done any good - the flash drives still won't work. I found a site today which at one time recommended the mobos but has since withdrawn their recommendation on the grounds of USB problems experienced by apparently many people. Since what I have involves USB drives my problem could well be down to that issue.

Currently I've decided to give up looking for a solution and hope that the next BIOS update sorts it. Since a WinXPE flash drive I have works OK I'm also going to see if I can extend it to cover most of what I would need in an emergency. If the USB problem isn't sorted by the end of the year I'll be looking at possibly replacing the mobo, probably with an MSI.

Tracey

Paul Black · 06 Sep 2021

Hello @TraceyW,

Just a thought.

[1] Can you see the information on the USB if you plug them in [ I know they are Bootable ]?
[2] Can you also see the information on the USB in Safe Mode?
[3] Have you tried creating ANOTHER [ Different ] Bootable USB to see if that works?

I hope this helps

Paul Black · 06 Sep 2021

Hello @TraceyW,

One FINAL thought . . .

In-Place-Upgrade - Repair Install

Information & Tutorials:

This is a Non-Destructive Process which keeps ALL your Apps, Programs, and Personal Data etc Intact . . .

IMPORTANT: This is an extract from the Tutorial below . . .

You will only be able to do a repair install of Windows 10 from within Windows 10. You will not be able to do a repair install at boot or in Safe Mode.
You will need at least around 10 GB + what Windows is currently using of free space available on the Windows drive.
The installation media (ex: ISO or USB) must be the same edition and same or newer build as your currently installed Windows 10. If it's not, then the repair install will fail.
The installation media (ex: ISO or USB) must be the same base language (aka: system default language) as your currently installed Windows 10. If it's not, then you will not keep anything.
If you have a 32-bit Windows 10, then you must use a 32-bit ISO or USB.
If you have a 64-bit Windows 10, then you must use a 64-bit ISO or USB.

> How to Do a Repair Install of Windows 10 with an In-Place Upgrade

Basically . . .

[1] Download the ISO to the Desktop.
[2] Right-click the ISO > Mount.
[3] Open File Explorer.
[4] Double-click the Mounted Drive to open it.
[5] Double-click setup.exe.
[6] Choose the Upgrade option.
[7] Select Change what to keep.
[8] Select One of the following . . .

Keep Personal Files and Apps.
Keep Personal Files Only.
Nothing.

[9] Unmount the ISO by right-clicking the Mounted Drive > Eject.

The only downside is that you could POSSIBLY lose some of your personalizations.

Recommendations:

DISABLE:

ANY Non-Microsoft . . .

Antivirus Software.
Firewall software.
Drive Encryption Software.

Temporarily Disable Secure Boot before performing the In-Place-Upgrade - Repair Install to be on the safe side.

I hope this helps.