Cut and Paste glitch

[InTents]

I have looked in the CBS.log file and I see these errors

2010-10-04 20:47:50, Info CSI 00000911 [SR] Cannot repair member file [l:26{13}]"nvwgf2umx.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000912 [SR] Cannot repair member file [l:24{12}]"nvwgf2um.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000913 [SR] Cannot repair member file [l:22{11}]"nvd3dum.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000914 [SR] Cannot repair member file [l:24{12}]"nvlddmkm.sys" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000915 [SR] Cannot repair member file [l:24{12}]"nvd3dumx.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000916 [SR] Cannot repair member file [l:18{9}]"nv_LH.inf" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000917 [SR] Cannot repair member file [l:26{13}]"nvwgf2umx.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000918 [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_nv_lh"
2010-10-04 20:47:50, Info CSI 00000919 [SR] Cannot repair member file [l:24{12}]"nvwgf2um.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 0000091a [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_nv_lh"
2010-10-04 20:47:50, Info CSI 0000091b [SR] Cannot repair member file [l:22{11}]"nvd3dum.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 0000091c [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_nv_lh"
2010-10-04 20:47:50, Info CSI 0000091d [SR] Cannot repair member file [l:24{12}]"nvlddmkm.sys" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 0000091e [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_nv_lh"
2010-10-04 20:47:50, Info CSI 0000091f [SR] Cannot repair member file [l:24{12}]"nvd3dumx.dll" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000920 [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_nv_lh"
2010-10-04 20:47:50, Info CSI 00000921 [SR] Cannot repair member file [l:18{9}]"nv_LH.inf" of nv_lh.inf, Version = 6.1.7600.16385, 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, file is missing
2010-10-04 20:47:50, Info CSI 00000922 [SR] This component was referenced by [l:178{89}]"Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.INF_nv_lh"

 

[InTents]

I have done some research on these .dll files and they all point to my Nvidia drivers. I am now going to uninstall, do a driver sweep and then reinstall and see if the problem goes away

 

[karlsnooks]

InTents,
Definitely look like you might want to go the site of the manufacturer of your graphics card/chip or mfg of your motherboard and get the very latest win 7 drivers.

Let us know how the repair efforts go.

 

[InTents]

Just uninstalled graphics drivers and have done another sfc scan and the CBS.log file shows the same problem files
I checked and the problem is still there

 

[karlsnooks]

Did you have an opportunity to fetch the latest and greatest and see if the install will at the same time remove the bad files?

 

[InTents]

Would updating my BIOS be useful? I have version 2.2 of my BIOS and there is 2.6 available. I have heard that flashing your BIOS is a last resort

 

[InTents]

Did you have an opportunity to fetch the latest and greatest and see if the install will at the same time remove the bad files?

Are you talking about my graphics drivers here?

 

[bobtran]

Be very careful when flashing the bios.....this is an opportunity to break/brick your pc. Only do this if it will help you with an issue you are having (do some research into what the updated bios will change) or will allow you to do something you can't without it.

That said it can help sometimes, I had to do a bios update when I changed from x86 to x64 on my XFX motherboard and a bios update allowed me to go to 2gb ram on my old Dell C640 laptop, I have not been sorry.

Nvidia Graphics drivers:
http://www.nvidia.com/Download/Find.aspx?lang=en-us
or
http://www.sevenforums.com/graphic-cards/602-latest-nvidia-forceware-video-drivers-windows-7-a.html

 

[InTents]

I already had the latest Nvidia drivers installed when I ran into this problem

 

[karlsnooks]

Would updating my BIOS be useful? I have version 2.2 of my BIOS and there is 2.6 available. I have heard that flashing your BIOS is a last resort

Very definitely update your BIOS. You must follow the manufacturer's instructions perfectly-no deviations, no creativity, no thinking a step is not necessary.

The only people who have bios update problems fail to follow instructions.

Nowadays, the bios update procedure is much easier and safer than just 5 years ago.

Update your BIOS.

 

[InTents]

I will do so. Thank you.
However this weird glitch has only happened recently. I agree that a BIOS update will be beneficial. But will it solve my problem?

I have just installed all the latest drivers for my motherboard.
All that is left is a BIOS update.
Any other thoughts?

 

[karlsnooks]

Perform the bios update.

 

[bobtran]

Agreed, do the bios update. Let us know how it goes.

 

[InTents]

I downloaded the latest BIOS for my motherboard from the MSI website.
Followed the instructions to the letter.
Had a successful reflashing. But then my pc did not want to boot.
Had the black screen with no beeps.
So now my motherboard is at the retailer. I'm hoping it will just get RMA and I'll get a new one with the latest BIOS. But I will see how it goes.

I really can't understand why it didn't work. I did everything in the instructions.
Well once I get my motherboard back, I will let you know if that solved this other issue

 

[InTents]

I have now received a new motherboard. The BIOS update went badly for an unknown reason. I do not think the BIOS has anything to do with the glitch I am having. Does anyone know why this is happening to me?

 

[InTents]

I have found out why it was happening. The files I were cutting and pasting are all files that have the small padlock on them when placed in Windows Explorer. This glitch does not happen with non-padlocked files. Does anyone know why this is or how I can remove the small padlock?

 

[Orbital Shark]

The padlock denotes that the 'Owner' of the file is 'SYSTEM' you need to take ownership of the files. The http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html tutorial will show you everything you need to know


OS

 

[InTents]

Thank you!!! Works amazingly!!! And has fixed the issue

 

[karlsnooks]

It may have worked, but there is a reason why the System was assigned as the owner. Believe me-win 7 knows best.

Let us know when you run across a fresh batch of problems caused by this "solution".