Reg.files/CBS Logs corrupt file(s) problem

[jordantall]

Hi,
I actually downloaded some language reg.files required for the application Microsoft Applocale but I accidentally install it(by just double-clicking on the reg.files) to the registry without Microsoft Applocale(I have not installed it yet)
So the problem crops up-->I can't open up files that are named with specific language. For example, when i attempt to open a winrar file, it will say something like 'cannot open files'

I thus try to scan it with sfc through cmd and it says there are corrupted files but it fails to repair them, asking me to refer the CBS.log file for further details.

The second problem is, I can't open CBS.log and I don't know what I should do to fix this.

I'm attaching the CBS.log(from windows\logs\CBS\) for review of my logs. thank you:lol:

by the way, apart from system repair, is there any other ways to restore the reg.files to default?

 

[niemiro]

Hello, and welcome to Sysnative :)

Can you please, if at all possible, upload/link me to the registry files that you imported? It's much easier to create an antidote if I have a sample of the poison

Thank you!

Richard

 

[jordantall]

this is the reg.file I imported

I was actually dealing with protected winrar files that the password contains some strange languages(not all English,may be there're some symbols)

then I downloaded this file without the installation of Microsoft applocale:roll eyes (sarcasti

 

[niemiro]

Hello again :)

Please download and run the 32bit edition of this tool: FixExec Download

If necessary, change the file extension to .scr to make it run.

That should undo the damage caused by the registry script.

---

Then I want you to run a different tool. This is for something minor I've noticed in your CBS.log. It should be a really quick fix, and will hopefully stop you coming back in a couple of months when the problem rears its head. I just need to use the SURT to double check that there is actually a problem, first, though.


Please download the System Update Readiness Tool from Microsoft ->here<-. Save the tool to a convenient location as it may be necessary to run it again.
After the download has completed, double-click the file and wait while it initializes.
Click Yes to begin installation.


Then, once it has completed installing (please be patient, it may take up to an hour (or very occasionally longer) to complete):

please upload your C:\Windows\Logs\CBS\CheckSUR.persist.log file just as you did with CBS.log.

Thank you!

Richard

 

[jordantall]

Hello again :)

Please download and run the 32bit edition of this tool: FixExec Download

If necessary, change the file extension to .scr to make it run.

That should undo the damage caused by the registry script.

---

Then I want you to run a different tool. This is for something minor I've noticed in your CBS.log. It should be a really quick fix, and will hopefully stop you coming back in a couple of months when the problem rears its head. I just need to use the SURT to double check that there is actually a problem, first, though.


Please download the System Update Readiness Tool from Microsoft ->here<-. Save the tool to a convenient location as it may be necessary to run it again.
After the download has completed, double-click the file and wait while it initializes.
Click Yes to begin installation.


Then, once it has completed installing (please be patient, it may take up to an hour (or very occasionally longer) to complete):

please upload your C:\Windows\Logs\CBS\CheckSUR.persist.log file just as you did with CBS.log.

Thank you!

Richard

I have gone through the first step successfully
but when double-clicked the System Update Readiness Tool(Windows6.1-KB947821-v32-x86)It said there was an installation error and ''A system-level error occurred while verifying trust.''