Main Forum > General Computer Support

.net4.8: 0x800f0922; Firefox: 0xc0000022

<< < (3/5) > >>

George:
Didn't you mean the SFCFix.txt that I've posted already?

Boggin:
No - that is what the sfc /scannow has reported.

You need to download SFCFix.exe from the link I'd posted in my earlier reply.

This needs to be run straight after a sfc /scannow as a CBS log can be volatile.

This is why I asked you to run another sfc /scannow so that the CBS log it produced would be fresh.

You will need to run another sfc /scannow and then download that program and run it.

That will produce its own report as to what it could or couldn't fix and what I want you to post.

George:
Oh, I did so but not immediately after sfc /scannow. I thought that the SFCFix.txt, which did say no corruption, was the result.

 All right next time I run the two right after each other. Do I need to download again, can't run the previous copy?

Boggin:
If you've already run SFCFix.exe it should have put a log onto your computer - can you dig it out and post it.

If it has already repaired what sfc /scannow couldn't then it will have that in its report, but to confirm, run another sfc /scannow which should report no integrity violations.

If that is the case, then try Windows Update again.

Another run of SFCFix.exe on a fully repaired sfc would produce a no error SFCFix.exe log.

George:
I ran SFCFix right after sfc /scannow as you said. It ran very long and then started DISM which ran even longer.
The end note of SFCFix and DISM log are enclosed, I couldn't find any log of SFCFix.

Navigation

[0] Message Index

[#] Next page

[*] Previous page