Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Replacing corrupted registry files


  • Please log in to reply
20 replies to this topic

#1 person223

person223

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:02 PM

Posted 15 April 2017 - 09:50 PM

Hello. I had a few processes lately start taking up an inordinate amount of memory when looking at the task manager, namely "Service Host: Windows Image Acquisition (WIA)." I reseearched what to do, so I checked for corrupted files using some code given for the command prompt. I was surprised by the results since I do not have an AMD processor, but I am worried about messing with those files. Do I have superfluous AMD software? As you can tell by the date, I haven't had much time to deal with this appropriately. Would it be safe to just delete these files? I do not think I have AMD software, and I have an Intel procecessor. As far as I can tell, I have no AMD hardware on my computer. For the corrupt printer driver registry file, I can just update the driver, right? I pasted the abbreviated log of an SFC scan below, but attached the full log.

 

2017-02-18 00:40:12, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2017-02-18 00:40:12, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2017-02-18 00:40:18, Info                  CSI    0000000c [SR] Verify complete
2017-02-18 00:40:18, Info                  CSI    0000000d [SR] Verifying 100 (0x0000000000000064) components
2017-02-18 00:40:18, Info                  CSI    0000000e [SR] Beginning Verify and Repair transaction

 

[truncated for ease of reading. I don't think these results are relevant, right?]

 

2017-02-18 00:56:48, Info                  CSI    000004b0 [SR] Verifying 100 (0x0000000000000064) components
2017-02-18 00:56:48, Info                  CSI    000004b1 [SR] Beginning Verify and Repair transaction
2017-02-18 00:56:55, Info                  CSI    000004b2 [SR] Verify complete
2017-02-18 00:56:56, Info                  CSI    000004b3 [SR] Verifying 100 (0x0000000000000064) components
2017-02-18 00:56:56, Info                  CSI    000004b4 [SR] Beginning Verify and Repair transaction
2017-02-18 00:57:08, Info                  CSI    000004b7 [SR] Verify complete
2017-02-18 00:57:08, Info                  CSI    000004b8 [SR] Verifying 100 (0x0000000000000064) components
2017-02-18 00:57:08, Info                  CSI    000004b9 [SR] Beginning Verify and Repair transaction
2017-02-18 00:57:11, Info                  CSI    000004bb [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-02-18 00:57:27, Info                  CSI    000004bd [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-02-18 00:57:27, Info                  CSI    000004be [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
2017-02-18 00:57:30, Info                  CSI    000004bf [SR] Verify complete
2017-02-18 00:57:30, Info                  CSI    000004c0 [SR] Verifying 100 (0x0000000000000064) components
2017-02-18 00:57:30, Info                  CSI    000004c1 [SR] Beginning Verify and Repair transaction

 

[truncated]

 

2017-02-18 01:07:44, Info                  CSI    000007f9 [SR] Verifying 50 (0x0000000000000032) components
2017-02-18 01:07:44, Info                  CSI    000007fa [SR] Beginning Verify and Repair transaction
2017-02-18 01:07:48, Info                  CSI    000007fd [SR] Verify complete
2017-02-18 01:07:48, Info                  CSI    000007fe [SR] Repairing 1 components
2017-02-18 01:07:48, Info                  CSI    000007ff [SR] Beginning Verify and Repair transaction
2017-02-18 01:07:49, Info                  CSI    00000801 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-02-18 01:07:49, Info                  CSI    00000803 [SR] Cannot repair member file [l:36{18}]"Amd64\CNBJ2530.DPB" of prncacla.inf, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-02-18 01:07:49, Info                  CSI    00000804 [SR] This component was referenced by [l:186{93}]"Microsoft-Windows-Printer-Drivers-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.INF_prncacla"
2017-02-18 01:07:49, Info                  CSI    00000805 [SR] Repair complete
2017-02-18 01:07:49, Info                  CSI    00000806 [SR] Committing transaction
2017-02-18 01:07:49, Info                  CSI    0000080b [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
 

Attached Files


Edited by person223, 16 April 2017 - 02:28 PM.


BC AdBot (Login to Remove)

 


#2 medab1

medab1

  • Members
  • 844 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:earth
  • Local time:11:02 PM

Posted 15 April 2017 - 09:57 PM

If you screwed up your registry & didn't make a backup you are pretty well screwed..

I suggest to people to make complete system images often.

I use Macrium Reflect.

Right now you are screwed.


Learn to take screenshots & add them to your posts. :thumbup2:

https://www.bleepingcomputer.com/forums/t/43088/how-to-capture-and-edit-a-screen-shot/#entry4532851

Learn to use Google Search.  :busy:

Make full system images to restore to if your computer goes bonkers.


#3 person223

person223
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:02 PM

Posted 15 April 2017 - 10:38 PM

I edited my OP.

 

I think I can just delete those AMD entries as they do not seem to be connected to any software, but maybe there is a better way to check. How did those files even get there?


Edited by person223, 16 April 2017 - 01:40 PM.


#4 FreeBooter

FreeBooter

  • Members
  • 3,137 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Turkey - Adana
  • Local time:06:02 AM

Posted 16 April 2017 - 05:16 AM

Please don't delete anything there was corrupted Windows system files and were repaired .


Posted Image


#5 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:02 PM

Posted 16 April 2017 - 10:43 AM

Rerun the sfc /scannow. 


The sfc /scannow log usually is very large, for this reason you should use a host website like Dropbox to post the log.  You can start a free 30 day trial.  Once you have loaded the log at Dropbox post a link to the website.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#6 person223

person223
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:02 PM

Posted 16 April 2017 - 01:39 PM

This is the full log of the SFC scan.

Attached Files



#7 JohnC_21

JohnC_21

  • Members
  • 23,976 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:02 PM

Posted 16 April 2017 - 01:48 PM

When you see AMD64 that's just nomenclature for 64bit, whether intel or AMD. 



#8 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:02 PM

Posted 16 April 2017 - 02:52 PM

Press the Windows key windowskey_zps092d5c75.png and the X key, in the menu that opens click or tap on Command Prompt (Admin).  This will open the Elevated Command prompt.
 
Copy and paste the command below in the Command Prompt, then press Enter.
 
dism /online /cleanup-image /restorehealth
 
Restart the computer to complete the repair.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#9 medab1

medab1

  • Members
  • 844 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:earth
  • Local time:11:02 PM

Posted 16 April 2017 - 03:58 PM

Press the Windows key windowskey_zps092d5c75.png and the X key, in the menu that opens click or tap on Command Prompt (Admin).  This will open the Elevated Command prompt.
 
Copy and paste the command below in the Command Prompt, then press Enter.
 
dism /online /cleanup-image /restorehealth
 
Restart the computer to complete the repair.

 

After running dism /online /cleanup-image /restorehealth run sfc /scannow in admin cmd prompt.

& reboot.

Whether this will correct your registry is debatabilitable.


Edited by medab1, 16 April 2017 - 04:02 PM.

Learn to take screenshots & add them to your posts. :thumbup2:

https://www.bleepingcomputer.com/forums/t/43088/how-to-capture-and-edit-a-screen-shot/#entry4532851

Learn to use Google Search.  :busy:

Make full system images to restore to if your computer goes bonkers.


#10 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:02 PM

Posted 16 April 2017 - 05:12 PM

After running dism /online /cleanup-image /restorehealth run sfc /scannow in admin cmd prompt.

& reboot.

Whether this will correct your registry is debatabilitable.

Let's wait and see what the DISM command produced.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#11 medab1

medab1

  • Members
  • 844 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:earth
  • Local time:11:02 PM

Posted 16 April 2017 - 07:41 PM

 

After running dism /online /cleanup-image /restorehealth run sfc /scannow in admin cmd prompt.

& reboot.

Whether this will correct your registry is debatabilitable.

Let's wait and see what the DISM command produced.

 

It could say dism succeeded in fixing the component store. (100%)

Hopefully.

Or "The needed files could not be downloaded."

In which case the "source" option should be tried.

With the "limit access" tag.

I've tried this with a mounted iso & an iso extracted iso on a usb drive neither of which worked.

It said the needed files could not be located.

This annoys me.

I did everything correctly but still got the error messages.

I noticed in the mounted & extracted iso that the dism files were different from the installed dism files.

I tried copying the iso dism files to to my computer.

Then dism would not work at all.

This really ticks me off.

If Microsoft provides the dism option it should work.

 

 

 

 


Learn to take screenshots & add them to your posts. :thumbup2:

https://www.bleepingcomputer.com/forums/t/43088/how-to-capture-and-edit-a-screen-shot/#entry4532851

Learn to use Google Search.  :busy:

Make full system images to restore to if your computer goes bonkers.


#12 person223

person223
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:11:02 PM

Posted 17 April 2017 - 05:26 PM

I had actually deleted a bunch of Toshiba bloatware just before posting here. I just got around to restarting my computer since then and the main processes using an inordinate amount of memory in the task manager are gone. Some processes still remain that may be problematic. Perhaps removing the rest of the Toshiba bloatware will fix it, but I was uncertain about the uselessness of every piece of software. I will do the suggested command prompt commands anyways given that the corrupt files should still perhaps present a problem.

#13 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:02 PM

Posted 18 April 2017 - 09:17 AM

There are two solutions you could use.

 

1st. Do a Refresh.  This will effectively reinstall Windows 8.1, but it will not delete your personal files.  It will uninstall any third party programs you have installed.

 

How to perform a Windows 8.1 Refresh.

You need to be aware that a refresh will remove all third party programs, but will not effect your personal files.
 
1. Open the Settings charm, tap/click on Change PC Settings.

2. Tap/click on Update and recovery, then tap/click on Recovery.

3. Under Refresh your PC without affecting your files, tap/click on Get started.

Follow the instructions as they appear.

 

2nd. Do a fresh installation using media which you would create using the Media Creation Tool.  This will resolve any problems with the operating system, the installation will be free of any bloatware.  You can find an excellent tutorial here.

 

 

You will need to install your programs of choice and download the update.

 

You will also need to go to the Toshiba website and download all of the drivers needed for your computer.  If you post the model of your Toshiba I will provide you with a link to the Toshiba website where you can download the drivers.  If you have any questions regarding which drivers you will need I can help you with this as well.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#14 medab1

medab1

  • Members
  • 844 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:earth
  • Local time:11:02 PM

Posted 18 April 2017 - 10:30 AM

The only corruption was an .xml file not present.

Otherwise everything was correct.

I'm not going to worry about it.


Learn to take screenshots & add them to your posts. :thumbup2:

https://www.bleepingcomputer.com/forums/t/43088/how-to-capture-and-edit-a-screen-shot/#entry4532851

Learn to use Google Search.  :busy:

Make full system images to restore to if your computer goes bonkers.


#15 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,590 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:08:02 PM

Posted 20 April 2017 - 11:30 AM

@person223

 

 

If your belief that the registry has corruption was based on the information in you first post you need to realize that what ever error were found are corrupted files.  From what I see in the sfc log I do not see any errors related to registry files.

 

I would suggest that you rerun sfc /scannow again to see if the corruption found previously has been repaired.  At the end of the log it should state all repairs were completed.       


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users