The application was unable to start correctly (0xc000007b)

[Vepar]

I can't start Steam anymore. I have no idea what happened, it worked yesterday and now it doesn't anymore and i didn't change a thing on my computer.

Things i tried:
- running as adnim
- reinstalling c++ and .net framework
- restarting computer
- reinstalling Steam
- allowing Steam through Firewall (it was already allowed)
- can't do an exception for it in my antivirus since it's not considered a thread, but i had that idea as well
- reinstalling DirectX

Possible related issue:
Windows suddenly stopped recognizing my monitor today. Drivers were up to date, but i did windows update and after a restart it did a disk check on its own and run an autofix thing and after it finally booted into windows, the monitor started working again.

Not sure if that has anything to do with Steam not opening but it started happening about the same time, maybe it's related, idk...

I'm out of ideas, can anyone help me?
I also sent a support ticket, but i'll write it here too just in case someone has an idea i can try.

[Vepar]

Diposting pertama kali oleh |<- Iceira ->|:

sure you do as you see fit, but alot of ppl have seen a rollback a update fix all, and then you update again you dont get the issue, try see it as fast recover step then from scrates.

Yes but, the update wasn't the problem, not by itself at least. The whole computer was acting strange well before i updated it with that last update. This was just where it finally broke.

Diposting pertama kali oleh |<- Iceira ->|:

ask any server or linux user they know how snap of system files can save our butt.
but anyway still user own problem what he do, gl with it.

I know it can, i wasn't even arguing that. I was just speaking from personal experience and bias. Wasn't giving a blanket statement about linux system snapshots...

Diposting pertama kali oleh |<- Iceira ->|:

keep in mind any tech person can tell you this , you dont get credit for things you should have done in the first places, and you only learn then you did not. hard words.

I'm... What? I'm not sure what you're geting at? I should have done what? What are you talking about?

Diposting pertama kali oleh |<- Iceira ->|:

you wont say things like that in a company to a customer or user, thank god for forum where user have chance to say it as it is.

Did i personally offend you in some way because i reinstalled windows? You said what as is? What needed to be said? And to whom? I'm still not sure what you're talking about...

[Ettanin]

Corrupted file system points to something likely being wrong with the drive it's stored on or damaged RAM. I wager it's the RAM considering the size of GW2 and Steam installations in general and the various related issues that show up as well.

A few Memtest86 runs (at least 4) without the bit fade test (test 10) and the hammer test (test 13) could paint a different picture. If there are errors, remove each RAM stick one by one and, to be sure, seat it in each of the slots, repeating the tests until you found the faulty one(s). Could be mainboard as well but RAM is more likely.

A Memtest86 ISO including a tool to burn it to a USB pen drive can be obtained here: https://www.memtest86.com/

Should the issues (eventually) repeat, I recommend checking your RAM.

[Vepar]

Diposting pertama kali oleh Ettanin:

Corrupted file system points to something likely being wrong with the drive it's stored on or damaged RAM. I wager it's the RAM considering the size of GW2 and Steam installations in general and the various related issues that show up as well.

A few Memtest86 runs (at least 4) without the bit fade test (test 10) and the hammer test (test 13) could paint a different picture. If there are errors, remove each RAM stick one by one and, to be sure, seat it in each of the slots, repeating the tests until you found the faulty one(s). Could be mainboard as well but RAM is more likely.

A Memtest86 ISO including a tool to burn it to a USB pen drive can be obtained here: https://www.memtest86.com/

Should the issues (eventually) repeat, I recommend checking your RAM.

I can run this regardless of the new Windows install right?
If so, i'll definitely run it a few times to see.

[Ettanin]

Diposting pertama kali oleh Vepar:

I can run this regardless of the new Windows install right?
If so, i'll definitely run it a few times to see.

Yes you can, it's a bootable DOS-like interface that runs the tests. It is to be booted from a USB pen drive, just like the Windows 10 setups. It will not overwrite your windows installation.

[Vepar]

Diposting pertama kali oleh Ettanin:

Diposting pertama kali oleh Vepar:

I can run this regardless of the new Windows install right?
If so, i'll definitely run it a few times to see.

Yes you can, it's a bootable DOS-like interface that runs the tests. It is to be booted from a USB pen drive, just like the Windows 10 setups. It will not overwrite your windows installation.

Nice! I'll check my RAM then.

[Ettanin]

Diposting pertama kali oleh Vepar:

Diposting pertama kali oleh Ettanin:

Yes you can, it's a bootable DOS-like interface that runs the tests. It is to be booted from a USB pen drive, just like the Windows 10 setups. It will not overwrite your windows installation.

Nice! I'll check my RAM then.

Disable tests 10 and 13. They are prone to false positives for consumer grade RAM.

[Vepar]

Diposting pertama kali oleh Ettanin:

Diposting pertama kali oleh Vepar:

Nice! I'll check my RAM then.

Disable tests 10 and 13. They are prone to false positives for consumer grade RAM.

Noted, thank you! :)

[Vepar]

Diposting pertama kali oleh UberFiend:

It's a CPU error code!!

0 zero zilch nought nada niente nothing to do with other components or drivers or magic fairies.

Meaning? What do you think happened and was the cause of this?

[Ettanin]

Diposting pertama kali oleh UberFiend:

It's a CPU error code!!

0 zero zilch nought nada niente nothing to do with other components or drivers or magic fairies.

Bollocks. That's not a CPU error code. That's the generic code number of the exception, which in dev terms could mean anything and is useless alone to determine the cause. If it was the CPU that has issues, Windows wouldn't boot.

[♡ D0c*underPANTS ♡]

hi boys and girls y have same issue wath to do tks

[Vepar]

Diposting pertama kali oleh D0c*underPANTS:

hi boys and girls y have same issue wath to do tks

Well, i ended up reinstalling windows, but try windows recovery tool to check if everything's ok on the system and let it fix what it thinks needs fixing.

[Iceira]

Diposting pertama kali oleh D0c*underPANTS:

hi boys and girls y have same issue wath to do tks

How about you actual bother gather crash report , as previous post already explaned, because reinstall and restore previous system driver will be seen as error is gone and can't be reproduce.

and we are only a user forum here, and you might be lucky if we can ID what crash log say.

and if you can get steam to work in safe boot mode, then its your pc that effcect by crapware that screw steam up, even steam support might want to look at it, if you can even ID it.

and its you jobe to even know it work before a update , and also your faulth for not make a system restore point before windows update, ( im sure many windows user are not aware of this, but as i said linux ppl are, but i can also say many windows user are not the first time a update scew it up. )

but people are use to np and not my job to take precautions before the update , i bet you need a windows crash before you learn that.

but as Vepar said even that can fail, so he just toke the fast easy way out of this, and we get it.

ps.
this post is not ment to hammer people in head, its just to late then you did not do the right thingy.

[Roble_Viejo]

Diposting pertama kali oleh Bee:

Since this started all of a sudden, and you're having other issues with Windows as well - I'd recommend running both sfc /scannow and DISM CheckHealth in command prompt - easy to do and google should tell you how.

For fun you can also go through in a chkdsk scan...might as well get them all in.

Hi! Just wanted to tell you the CMD elevated command "DISM RestoreHealth" and a restart fixed it!

I was about to lose my 800GB Steam Folder, it wouldnt even let me check the files, it said "The Folder is Corrupted and Unreadable" thank God I didnt just delete the folder and reinstalled Steam, it would had taken me weeks to download everything again.

For the other people looking for answers:
- "Elevated Command" means to "Run CMD as Administrator", and if you use the "Restore Health" command you will see a loading screen checking all files the next time you boot your PC.

I have no idea what broke specifically tho, but Steam updated the day before, maybe I turned off the PC before it finished updating or something.

[Elucidator]

Diposting pertama kali oleh Roble Viejo:

Hi! Just wanted to tell you the CMD elevated command "DISM RestoreHealth" and a restart fixed it!

I was about to lose my 800GB Steam Folder, it wouldnt even let me check the files, it said "The Folder is Corrupted and Unreadable" thank God I didnt just delete the folder and reinstalled Steam, it would had taken me weeks to download everything again.

For the other people looking for answers:
- "Elevated Command" means to "Run CMD as Administrator", and if you use the "Restore Health" command you will see a loading screen checking all files the next time you boot your PC.

I have no idea what broke specifically tho, but Steam updated the day before, maybe I turned off the PC before it finished updating or something.

This thread is from 2021. You're necroposting, which would be fine if you had input that was correct at least and if this wasn't a looking-for-help thread.

OP likely no longer has that issue after two years. If they do they could continue to post. You provide no new input for OP.

No, dism.exe /Online /Cleanup-Image /RestoreHealth doesn't fix this issue. What it does is 'fix issues with the Windows Component Store'.
It can for example be used to fix the System File Checker tool (sfc), allowing it to work properly.
sfc /scannow fixes windows system components (such as Windows Update) and the registry.

What fixed things for you, the tool that made your PC scan stuff upon boot, was chkdsk (checkdisk). A tool that can fix the Journaling File System file and other file system issues. Likely, the cause in your case of this issue was a Journaling File System file issue. You can tell this yourself if you look through Event Viewer, which holds the log of the checkdisk application.

[Vepar]

OP isn't even on Windows anymore lol.
And terminal in linux is a bit different from CMD.