SEARCH

The How-To Geek Forums Have Migrated to Discourse

How-To Geek Forums / Windows 7

webcam suddenly not detected on hp windows7

(29 posts)
  • Started 1 year ago by onestepawayfromarmageddon
  • Latest reply from G41M
  • Topic Viewed 2517 times

onestepawayfromarmageddon
Posts: 43

Hello,

Any help on the following would be much appreciated. This concerns my integrated webcam on my HP DV7 notebook (Windows 7, x64). I have been using this notebook for about 7 months now, and also the webcam usually about once per month or so (through Skype or Cyberlink Youcam). The last time that I used the webcam was in early October. No problems each time in the past that I had used the webcam. The Windows 7 Home premium (service pack 1) I am using came packaged together on the HP when I bought the notebook.

A few days ago, when I tried to open Cyberlink Youcam, it showed an error message on opening: “Warning”, followed by “No webcam detected. Try plugging in a webcam into your computer now. If you are using an integrated webcam, make sure it is turned on.”

Ok, so, troubleshooting:
1. HP DV7 does not have a separate webcam on/off button that I know of. In the past whenever, I opened up Youcam (or Skype), the webcam started operating automatically.
2. Ok, first step: turn off computer. Now, turn on computer again. Open program. Still same result.
3. I then searched around on the web, and tried some already posted advice, such as going to websites that test webcams (using the “allow” button on the screen on the flash player). One of the sites even allows you to not only test webcam, but also record video (and audio combined). The result of all these site tests – audio is working, but no video.
4. I opened Skype to run. Under “tools/options”, Skype tells me to close any other program that might be using the webcam, as it cannot access the webcam. Problem is, no other program is running that uses a webcam. After one day, a retry of the webcam using Skype shows the message “Skype couldn’t find a webcam. With a webcam, you can make free video calls…..”.
5. So apparently, it is not a problem with Cyberlink Youcam, nor with any other programs that use the webcam. Because no program at all (even remotely from the web) can even detect the integrated webcam.
6. I have also tried rolling back Windows using system restore to about 1 month ago, to see if maybe there was some kind of update/patch that might have disabled/conflicted with Youcam/webcam driver update/software. No luck there. Post rollback, same result.
7. I also went to “Device Manager” under “Control Panel”. Under “Sound, video and game controllers”, I see “Cyberlink WebCam Virtual Driver”. Double clicking on this, gives the properties box, which tells me “This device is working properly”. I see no other video input/imaging device listed. There are also no exclamation marks next to any of the devices to indicate that any of them is malfunctioning.
8. I have tried to open Youcam and/or Skype quite a few times in the last few days, trying this or that, or just repetitiously trying the same things as above to see if there happened to suddenly be any changes, but no luck: still the same result every time.

Does anyone happen to have any ideas what is going on, and/or how I can resolve this problem?

Here is also a question: is there, within BIOS or that part of the computer that is generally not accessible to idiots like me, some screen somewhere where the webcam can be turned on and off? I ask this question because, on a PREVIOUS notebook, while a technician/engineer was fiddling around a few years ago, trying to figure out how to repair an unrelated problem on an old notebook of mine, he managed to inadvertently somehow, select/change something such that the optical drive on the notebook suddenly would not open (when you pushed the open/close button – had to use a pin to insert into the hole to get it to open). That is to say, if it is actually possible to control even physical/mechanical opening functions from BIOS (or that area where the blue screen lies, and lots of other pages like that), then maybe there is a page there that actually can turn off/on the webcam. Maybe somehow, for some unknown (and highly unlikely) reason, somehow, the webcam has been shut off (mechanically).

Have also been having a problem with another program on my HP, if you would like to read about it, please see other thread I started called: “Previously working Sony program suddenly not working on Windows 7 hp”

thanks to all for your attention, and if anyone can help, that would be absolutely brilliant. merry christmas to all.

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43
 
GuiltySpark
Posts: 4024

Open up a command prompt in Elevated mode and type sfc /scannow

Does it show any violations etc ?

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

hi there, guilty spark. good to hear from you again. thanks for checking in here.

sfc scannow gives the following result:

"wrp found corrupt files but was unable to fix some of them. details are included in the cbs.log windir\logs\cbs\cbs.log. for example c:\windows\logs\cbs\cbs.log"

when i try to open the filepath exampled, i am afforded the pop up "access denied".

any thoughts?

Posted 1 year ago
Top
 
GuiltySpark
Posts: 4024

You can view them in Safe mode, check the dates as there may be many.

Posted 1 year ago
Top
 
raphoenix
Posts: 14920

There are (3) Blue Links in the article to Expand.
There name is: Click here to show/hide solution
http://support.microsoft.com/kb/929833#method3

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

hi guilty spark,

i went to safe mode and successfully extracted the exampled cbs log. it is however, pretty long, and aside from seeing some very obvious repeated entries, i am not sure what i am supposed to be looking for. i could send/post a copy of the log, but i am not sure where i should do that, as it is really rather long - i don't want to clog up htg airspace. do you have any ideas? am sure there are quite simple solutions to this, but it is almost 6 in the morning here, and i am pretty past able to think clearly at this point. may have to come back to you on this tomorrow night or day after (no internet at home).

raphoenix, i read your three links, and will try them tomorrow. or as much of them as i can understand. will post back to you on the results as soon as i am able to. please hang in there for the moment, and check back.
here right now, without going to command prompt, the instruction on the second blue link (show/hide solution), point #3,
"Type sfcdetails.txt in Search programs and files, and then press Enter."
when i type this in the search box, it says "no items match your search". but will give #2 a go tomorrow, and also the third blue link.

thanks guys, out for now.

oh wait, one more thing, guilty spark, in safe mode, post sfc scannow, when i try to open youcam, i am shown a message "you do not have the compatible vga hardware or driver to run youcam". when i try to run skype, i get the same message as before "can't start video. try closing other program that might be using your webcam". and for the sony dve, same result as in normal mode. "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available".

Posted 1 year ago
Top
 
GuiltySpark
Posts: 4024

May just be a shot in the dark but try this :

Hold Winkey+R

Type msconfig into the Run box

Select Start tab and uncheck Skype and youcam

Apply/OK and restart computer

Download the TDSSkiller .exe file : http://support.kaspersky.com/5350

Run it just to check no malicious programs are using your webcam services.

As for the log file, they are very long what you should be looking for when you carefully go through it is a section that tells of fixes not made, depending on where the problem is this may help to work out if it is a windows corruption or a third party.
Unfortunately at this point it is difficult to tell without seeing first hand.

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

hi guys,

thanks for your patience. sorry about the delay, needed to sleep after 2 days without rest - was not able to think nor see straight anymore.

raphoenix: i followed your instructions - for the second blue link, the results of the sfcdetails.txt file are that the files that were not repaired are the following:

2012-12-25 06:02:44, Info CSI 000001ce [SR] Verifying 100 (0x0000000000000064) components

2012-12-25 06:02:44, Info CSI 000001cf [SR] Beginning Verify and Repair transaction

2012-12-25 06:02:46, Info CSI 000001d1 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-12-25 06:02:46, Info CSI 000001d3 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-12-25 06:02:46, Info CSI 000001d4 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.NetFx3"

this above listed group showed up about two-thirds way through the log, and then at the end of the log, came the following group:

2012-12-25 06:06:01, Info CSI 000002ea [SR] Verifying 9 components

2012-12-25 06:06:01, Info CSI 000002eb [SR] Beginning Verify and Repair transaction

2012-12-25 06:06:02, Info CSI 000002ed [SR] Verify complete

2012-12-25 06:06:02, Info CSI 000002ee [SR] Repairing 1 components

2012-12-25 06:06:02, Info CSI 000002ef [SR] Beginning Verify and Repair transaction

2012-12-25 06:06:02, Info CSI 000002f1 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-12-25 06:06:02, Info CSI 000002f3 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-12-25 06:06:02, Info CSI 000002f4 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.NetFx3"

2012-12-25 06:06:02, Info CSI 000002f6 [SR] Repair complete

2012-12-25 06:06:02, Info CSI 000002f7 [SR] Committing transaction

2012-12-25 06:06:02, Info CSI 000002fb [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

can anyone help me to decipher the above please? i am not sure how the above would be translated into the next steps as listed in your blue linked section #3, raphoenix?

but, guilty spark, does the above also answer your question about "violations, etc"?

thought i would post the above first, will get to your latest suggestion about msconfig and kaspersky now, and come back to you with an answer when done. thanks again, guys. all this is much appreciated..

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

hi guilty spark,

i did as indicated, removed from startup programs youcam (skype already previously disabled many months ago) downloaded and ran the tdss killer, result: 465 objects scanned/processed, "no threats found".

did it twice. same result.

do have a sense it might be some sort of viral infection. had been taking real good care of this new computer, not interchanging flash drives etc., unlike with previous machine. but slipped up about 1.5 months ago, when a student of mine gave me a drive with some files on it that were to large to be emailed. my avast AV identified one virus on the drive (scanned before opening the drive), which it took care of, but even after, just had a sense that something else had entered the system (immediately after opening the drive, the icons on the desktop started to flash/blink like they do after a fresh restart post windows updates, and often do the same now, on restart, even though no windows updates downloaded) . maybe just freaky paranoid, though...?

hopefully someone please can help me find a way out of this one....

Posted 1 year ago
Top
 
GuiltySpark
Posts: 4024

Re-read Ricks link and select the extension link that says "If the System File Checker tool cannot repair a file, follow these steps:"

This should allow you to repair the necessary files.

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

hi guiltyspark,

looking at the cbs log, it looks like what you would be looking for would be (results of) the POQs, no?

although,... initially, there appear to be some number of "SQM: Failed to"'s such as:

2012-12-25 00:53:03, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2012-12-25 00:53:03, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]

there are also a number of other "failed to"'s, such as:

2012-12-25 01:40:58, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-12-25 01:40:58, Info CBS Session: 30269949_3581394960 initialized by client WindowsUpdateAgent.

after this come the POQs -
POQ0, POQ1, POQ2.....

for example:

POQ 1 starts:

POQ 1 ends.
2012-12-25 05:56:52, Info CSI 00000010 [SR] Verify complete
2012-12-25 05:56:52, Info CSI 00000011 [SR] Verifying 100 (0x0000000000000064) components
2012-12-25 05:56:52, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2012-12-25 05:56:53, Info CSI 00000013 Repair results created:

and then we get to the POQs which have more information:

POQ 11 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\35f8ffa021e2cd01b20400006c1b541b._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\35f8ffa021e2cd01b30400006c1b541b.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:246{123}]"\SystemRoot\WinSxS\Temp\PendingRenames\d57e01a121e2cd01b40400006c1b541b.$$_diagnostics_system_audio_9d2751b7c84ca0f1.cdf-ms", Destination = [l:158{79}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_audio_9d2751b7c84ca0f1.cdf-ms"
3: Move File: Source = [l:258{129}]"\SystemRoot\WinSxS\Temp\PendingRenames\158c04a121e2cd01b50400006c1b541b.$$_diagnostics_system_audio_en-us_9fb258d76056760d.cdf-ms", Destination = [l:170{85}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_audio_en-us_9fb258d76056760d.cdf-ms"
4: Move File: Source = [l:244{122}]"\SystemRoot\WinSxS\Temp\PendingRenames\f61f09a121e2cd01b60400006c1b541b.$$_diagnostics_system_aero_8b2c42561936b3f0.cdf-ms", Destination = [l:156{78}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_aero_8b2c42561936b3f0.cdf-ms"
5: Move File: Source = [l:256{128}]"\SystemRoot\WinSxS\Temp\PendingRenames\f61f09a121e2cd01b70400006c1b541b.$$_diagnostics_system_aero_en-us_1a668ac520a43d24.cdf-ms", Destination = [l:168{84}]"\SystemRoot\WinSxS\FileMaps\$$_diagnostics_system_aero_en-us_1a668ac520a43d24.cdf-ms"
6: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\376218a121e2cd01b80400006c1b541b.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
7: Move File: Source = [l:242{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\18f61ca121e2cd01b90400006c1b541b.$$_system32_manifeststore_7d35b12f9be4c20e.cdf-ms", Destination = [l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_system32_ma
2012-12-25 05:57:12, Info CSI nifeststore_7d35b12f9be4c20e.cdf-ms"
8: Move File: Source = [l:234{117}]"\SystemRoot\WinSxS\Temp\PendingRenames\f88921a121e2cd01ba0400006c1b541b.$$_help_windows_en-us_b594929e73669c5e.cdf-ms", Destination = [l:146{73}]"\SystemRoot\WinSxS\FileMaps\$$_help_windows_en-us_b594929e73669c5e.cdf-ms"
9: Move File: Source = [l:228{114}]"\SystemRoot\WinSxS\Temp\PendingRenames\981023a121e2cd01bb0400006c1b541b.$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms", Destination = [l:140{70}]"\SystemRoot\WinSxS\FileMaps\$$_help_help_en-us_91e6e7979a9bf9c6.cdf-ms"
10: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\b9b12aa121e2cd01bc0400006c1b541b.$$_apppatch_1143992cbbbebcab.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_apppatch_1143992cbbbebcab.cdf-ms"
11: Move File: Source = [l:236{118}]"\SystemRoot\WinSxS\Temp\PendingRenames\f9be2da121e2cd01bd0400006c1b541b.$$_apppatch_apppatch64_e39bab3b20714e20.cdf-ms", Destination = [l:148{74}]"\SystemRoot\WinSxS\FileMaps\$$_apppatch_apppatch64_e39bab3b20714e20.cdf-ms"

POQ 11 ends.
2012-12-25 05:57:12, Info CSI 00000038 [SR] Verify complete
2012-12-25 05:57:13, Info CSI 00000039 [SR] Verifying 100 (0x0000000000000064) components
2012-12-25 05:57:13, Info CSI 0000003a [SR] Beginning Verify and Repair transaction
2012-12-25 05:57:16, Info CSI 0000003b Ignoring duplicate ownership for directory [l:46{23}]"\??\C:\Windows\SchCache" in component Microsoft-Windows-Active-Directory-Services-Interface-LDAP-Provider, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

2012-12-25 05:57:17, Info CSI 0000003c Repair results created:

there are also a whole bunch of "Ignoring duplicate ownership for directory"s in a row, but i am not sure those are what you are searching for.

wait, i think i have it now. i see the first "cannot repair..."

POQ 79 starts:

POQ 79 ends.
2012-12-25 06:02:44, Info CSI 000001cd [SR] Verify complete
2012-12-25 06:02:44, Info CSI 000001ce [SR] Verifying 100 (0x0000000000000064) components
2012-12-25 06:02:44, Info CSI 000001cf [SR] Beginning Verify and Repair transaction
2012-12-25 06:02:46, Info CSI 000001d0 Hashes for file member \SystemRoot\WinSxS\msil_system.workflow.componentmodel_31bf3856ad364e35_6.1.7601.17514_none_ea7fd6352ea9de2d\System.Workflow.ComponentModel.dll do not match actual file [l:68{34}]"System.Workflow.ComponentModel.dll" :
Found: {l:32 b:nbNP4olAvEQ1YhBE6pzJ/5L7sF8g/LA6r/nt/8j8EHc=} Expected: {l:32 b:l0XqW9MYcxcnBbQExCkcg+l1S+S7IW/vDrV87K1g4cM=}
2012-12-25 06:02:46, Info CSI 000001d1 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-12-25 06:02:46, Info CSI 000001d2 Hashes for file member \SystemRoot\WinSxS\msil_system.workflow.componentmodel_31bf3856ad364e35_6.1.7601.17514_none_ea7fd6352ea9de2d\System.Workflow.ComponentModel.dll do not match actual file [l:68{34}]"System.Workflow.ComponentModel.dll" :
Found: {l:32 b:nbNP4olAvEQ1YhBE6pzJ/5L7sF8g/LA6r/nt/8j8EHc=} Expected: {l:32 b:l0XqW9MYcxcnBbQExCkcg+l1S+S7IW/vDrV87K1g4cM=}
2012-12-25 06:02:46, Info CSI 000001d3 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-12-25 06:02:46, Info CSI 000001d4 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.NetFx3"
2012-12-25 06:02:47, Info CSI 000001d5 Repair results created:

and also:

POQ 122 starts:

POQ 122 ends.
2012-12-25 06:06:02, Info CSI 000002ed [SR] Verify complete
2012-12-25 06:06:02, Info CSI 000002ee [SR] Repairing 1 components
2012-12-25 06:06:02, Info CSI 000002ef [SR] Beginning Verify and Repair transaction
2012-12-25 06:06:02, Info CSI 000002f0 Hashes for file member \SystemRoot\WinSxS\msil_system.workflow.componentmodel_31bf3856ad364e35_6.1.7601.17514_none_ea7fd6352ea9de2d\System.Workflow.ComponentModel.dll do not match actual file [l:68{34}]"System.Workflow.ComponentModel.dll" :
Found: {l:32 b:nbNP4olAvEQ1YhBE6pzJ/5L7sF8g/LA6r/nt/8j8EHc=} Expected: {l:32 b:l0XqW9MYcxcnBbQExCkcg+l1S+S7IW/vDrV87K1g4cM=}
2012-12-25 06:06:02, Info CSI 000002f1 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-12-25 06:06:02, Info CSI 000002f2 Hashes for file member \SystemRoot\WinSxS\msil_system.workflow.componentmodel_31bf3856ad364e35_6.1.7601.17514_none_ea7fd6352ea9de2d\System.Workflow.ComponentModel.dll do not match actual file [l:68{34}]"System.Workflow.ComponentModel.dll" :
Found: {l:32 b:nbNP4olAvEQ1YhBE6pzJ/5L7sF8g/LA6r/nt/8j8EHc=} Expected: {l:32 b:l0XqW9MYcxcnBbQExCkcg+l1S+S7IW/vDrV87K1g4cM=}
2012-12-25 06:06:02, Info CSI 000002f3 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-12-25 06:06:02, Info CSI 000002f4 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.NetFx3"

2012-12-25 06:06:02, Info CSI 000002f5 Repair results created:

actually, this appears to my highly untrained eyes to be the only sets of cannot repair member files that show up. might be wrong though. might be very wrong... wait a minute, how about we use dropbox...

hmmm.... it looks like this cbs log tallys with the sfcdetails.txt. the sfcdetails seems to be a more condensed version, though, yes, raphoenix? yes, yes, i guess you are just about sighing and shaking head sadly right now..... sorry, even after a few years of ownership of a notebook, still very inexperienced in this area here. bear with me, please...

1. okay, so i am putting both these files (complete) into dropbox (so that i don't clog up htg bandwidth or storage).
2. so that you guys don't have to download dropbox onto your computers, you can just go to https://www.dropbox.com/login?lhs_type=anywhere.
3. once there, use this email as login XXXXXXXXX.
4. use this password XXXXXXXXX.
5. the page will automatically flip and you can see and access the relevant files.

Edited: for posters safety Gmod.

Posted 1 year ago
Top
 
GuiltySpark
Posts: 4024

onestep... ,

Please don't post your dropbox account details they can be used against you.

Take a look here and read through, you may need to rebuild the bcd file : http://windows.microsoft.com/e.....0x800F0A12

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

hi guiltyspark,

i understand and have tried to do what you are saying, but i don't know how to do what is described.

can you help me to translate, for example,

"CSI 000001d1 [SR] Cannot repair member file [l:68{34}]"System.Workflow.ComponentModel.dll" of System.Workflow.ComponentModel, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_MSIL (8), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch"

into a path and filename? as instructed by below:

"At an elevated command prompt, copy and then paste (or type) the following command, and then press ENTER:
takeown /f Path_And_File_Name
For example, type takeown /f E:\windows\system32\jscript.dll." ?

and where would i go to find a "known good copy of the file" as indicated in #3?. should i be going to the recovery disk?

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

ok, guiltyspark,
i have deleted the dropbox account, so no one will be able to access the files in that account anymore. sorry, did not mean to offend anyone. just did not want to use up too much of htg's resource, nor to clog up airspace.
thank you for the warning.

i think i am responding one post slower to you at the moment, please take my previous post as response not to your post on rebuilding bcd file, but on the link given by raphoenix. futher to that post, would the filepath for that method be
"takedown /f c:\windows\system64\System.Workflow.ComponentModel.dll"?

also, i still do not know where to go to get a known good copy of the file.

i took a look at the link you posted, which apparently is for problems in installing sp1.

with regards to rebuilding the bcd store/file, which is located in the final section, i take it what i should be doing is:
1. go to Advanced Boot Options screen, and Repair your computer
2. and then after that, go to Command Prompt and type Bootrec /rebuildbcd

i take it this is where i should stop, yes? just restart computer, but not follow through with a reinstallation of sp1?

thanks again for your help.

Posted 1 year ago
Top
 
GuiltySpark
Posts: 4024

Ok disregard my last post about BCD as I have become confused between other threads in my 'merriment' too many HobGoblins (ales). Sorry :)

If you have an installation disc I would boot into it and select the repair my computer option, run three times.

I'll have to do some digging on the directory as I don't have win7 to work with at the moment.

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

no worries, g-spark. tis the season to be jolly.
appreciate all the time and help you have given already. if i could i would add more pints to your table.

i will run the repair my computer as you suggested, and post back here with results of that either tomorrow or day after. late now, out for tonight.
thanks again, to both you and raphoenix for your help and guidance.

Posted 1 year ago
Top
 
GuiltySpark
Posts: 4024

At this point I would try the sfc scan with the install disc run a few times to see if it makes a difference.

Posted 1 year ago
Top
 
G41M
Posts: 902

I might be wrong but I noticed no Imaging devices in the picture of Device Manager where the webcam should be. It may by OFF or have failed. When you use Skype or Youcam, can you see the webcam indicator light ON?

Posted 1 year ago
Top
 
onestepawayfromarmageddon
Posts: 43

guiltyspark, i do not have the install discs with me. they are in the u.s., while i, happen to be all the way over in thailand.

here is a question. bear with me, i have tried to google the answer, but cannot seem to find a direct or straight answer, or maybe i am just too simple minded. it is a dumb beginner question by the way, which is what i am, in case you had not noticed before....

what is the difference between windows' system restore and system image?
previously, i had posted that i had rolled back windows using system restore, images of which are located/kept within c drive itself (yes?). but i have also created each month in the last 7 months with this new computer, a system image, on an external drive.
i also previously posted that when i used system restore, i rolled it back 1 month, to no avail/no difference in terms of solving the problems with webcam or the sony audio program. would it make a difference if i tried using the images i created with system image on the external hdd? or are these two jist about the same thing? if they are different, should i be taking any precautions before i do a recovery or whatever it is called from (this externally saved) system image? at what point should i do this attempted recovery, i take it i should go through all pains to (try to) do "repair my computer" first?

also, windows7 has a utility, is maybe the word for it?, built into the computer/os itself, so that i can (supposedly) "repair my computer" without using the install discs. what i have to do is to f8 to the abos, and the first choice it gives me is "repair your computer". so this is what i did, but when i entered that highlighted choice, it returned a screen that said, "windows failed to start. a recent hardware or software....... insert your windows installation disc and restart your computer" the error code it gave was 0xc000025. "The boot selection failed because a required device is inaccessible".
but this does not make sense. windows is running, otherwise i wouldn't be posting right now. is this message supposed to mean that even though there is a selection choice in abos for "repair your computer", it still requires the install disc? this is what i am thinking now, that (it requires the external disc even though the "highlighted choice" may be built into windows7 already, and that) because/given that i did not insert said disc, this is why i get the error message. is this right? or is this a new and different problem completely?

hi g41m, thanks for your post reply. you are not wrong. i had read in numerous posts around the web when i googled for help on this, that says that there should be "imaging devices" in device manager. this is what i had alluded to in the initial post. of course, i cannot tell you whether because it is no longer there, that is why the webcam does not work, because i never had cause to look there before the webcam failed to work. or when i did, i did not pay attention to imaging devices.
but the webcam is integrated, and there is no on/off button for this hp notebook. in the past, when i turned on youcam or skype, automatically the webcam would start, and the indicator light would come on.
there is a entry in device manager for the youcam driver, as you may have seen, from the pictures, that says the youcam driver is working fine. but is this youcam driver, different that the webcam driver?

Posted 1 year ago
Top
 



Topic Closed

This topic has been closed to new replies.