I then tried to copy the file to the desktop and got "the action can't be completed because the file is open in windows modules installer"

code 80070002 windows 7
Started by
panthertooth
, Apr 07 2013 12:47 AM
#16
Posted 18 April 2013 - 10:03 AM

#17
Posted 18 April 2013 - 11:26 AM

Hi panthertooth,
Sorry about that, I misread your post. Nothing should have a read lock on the CBS log so I would like you to reboot your computer then attempt this command please:
Command Prompt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Tom
Sorry about that, I misread your post. Nothing should have a read lock on the CBS log so I would like you to reboot your computer then attempt this command please:
Command Prompt
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Click on the Start
button and in the search box, type Command Prompt
- When you see Command Prompt on the list, right-click on it and select Run as administrator
- When command prompt opens, copy and paste the following commands into it, press enter after each
copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
- This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
Tom
#19
Posted 19 April 2013 - 09:04 AM

Hi panthertooth,
Thanks for the log. I've reviewed your CBS log and have identified the corruption:
To be able to fix this, I will have to repair your COMPONENTS registry hive by editing the raw binary of it. Can you zip up and upload the following file please:
C:\Windows\system32\config\COMPONENTS (it has no file extension)
It will be too large to attach so you'll have to upload it to SendSpace.
Tom
Thanks for the log. I've reviewed your CBS log and have identified the corruption:
2013-04-18 18:42:37, Error CSI 0000000d (F) STATUS_OBJECT_NAME_NOT_FOUND #105113# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0}, da = (KEY_READ|DELETE|KEY_WOW64_64KEY), oa = @0xe2d1c0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[218]"\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.17592 (win7sp1_gdr.110408-1631)\ComponentFamilies\amd64_microsoft-windows-w..oyment-languagepack_31bf3856ad364e35_en-us_fa91c545bdb2a540\v!6.1.7601.17514"; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 14865800 (0x00e2d588))[gle=0xd0000034] 2013-04-18 18:42:37, Error CSI 0000000e@2013/4/19:01:42:37.103 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(3676): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null) [gle=0x80004005] 2013-04-18 18:42:37, Error CSI 0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #105112# from Windows::Rtl::SystemImplementation::CKey::OpenExistingKey(f = 2, da = (KEY_READ|DELETE), oa = @0xe2d620, key = NULL, disp = (null))[gle=0xd0000034] 2013-04-18 18:42:37, Error CSI 00000010 (F) STATUS_OBJECT_NAME_NOT_FOUND #105100# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034] 2013-04-18 18:42:37, Error CSI 00000011 (F) STATUS_OBJECT_NAME_NOT_FOUND #56165# from Windows::Rtl::SystemImplementation::CKey::DeleteRecursively(...)[gle=0xd0000034] 2013-04-18 18:42:37, Info CBS Failed to get CSI store. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 2013-04-18 18:42:37, Error CBS Failed to initialize store parameters with boot drive: and windows directory: [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
To be able to fix this, I will have to repair your COMPONENTS registry hive by editing the raw binary of it. Can you zip up and upload the following file please:
C:\Windows\system32\config\COMPONENTS (it has no file extension)
It will be too large to attach so you'll have to upload it to SendSpace.
Tom
#20
Posted 07 May 2013 - 09:27 PM

Sorry for the delay, My friend brought her computer to someone and had it reformatted so you can close this topic now.
Thanks for all your help
Thanks for all your help

#21
Posted 08 May 2013 - 01:49 AM

Hi panthertooth,
Thank you for letting us know. This whole problem could've been solved by changing one registry key so a clean install is a bit overkill but either way I'm glad you've managed to solve this problem.
Tom
Thank you for letting us know. This whole problem could've been solved by changing one registry key so a clean install is a bit overkill but either way I'm glad you've managed to solve this problem.
Tom
#22
Posted 08 May 2013 - 09:40 AM

unfortunately that was not the only problem she was also having a lot of BSOD's and also World of Warcraft was crashing a fair amount, My thinking is that her registry had been messed up due to her using some sort of "free registry cleaner" on a frequent basis. The person that had initially set up her PC had told her it was "ok" to use that and that it would "clean" her computer.
Again thanks for all your help,
Panthertooth
Again thanks for all your help,
Panthertooth
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






