New
#21
...it means I goofed!
I've uploaded a new copy of the cjdac.zip file with the proper structure - try the whole procedure again.
(it's what comes of doing this before finishing the first cup of coffee of the day!)
...it means I goofed!
I've uploaded a new copy of the cjdac.zip file with the proper structure - try the whole procedure again.
(it's what comes of doing this before finishing the first cup of coffee of the day!)
I must be losing my touch!...
I'l check through the details and see if I can work out why those replacements didn't work and get back to you.Code:Line 14598: 2015-03-03 19:39:10, Info CSI 00000359 [SR] Repairing 3 components Line 14599: 2015-03-03 19:39:10, Info CSI 0000035a [SR] Beginning Verify and Repair transaction Line 14602: 2015-03-03 19:39:10, Info CSI 0000035c [SR] Cannot repair member file [l:42{21}]"getevent.types.ps1xml" of Microsoft-Windows-PowerShell, Version = 7.1.7601.16398, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 14605: 2015-03-03 19:39:10, Info CSI 0000035e [SR] Cannot repair member file [l:58{29}]"PowerShellTrace.format.ps1xml" of Microsoft-Windows-PowerShell, Version = 7.1.7601.16398, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 14608: 2015-03-03 19:39:10, Info CSI 00000360 [SR] Cannot repair member file [l:22{11}]"acppage.dll" of Microsoft-Windows-Application-Experience-Tools, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch Line 14611: 2015-03-03 19:39:10, Info CSI 00000362 [SR] Cannot repair member file [l:24{12}]"services.msc" of Microsoft-Windows-ServicesSnapIn, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
Definitely a case of me losing my touch! - plus one of the patches required is quite obscure...
I've uploaded a file - cjdad.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\cjdad
hit the enter key - if you get a 'Not Found' error try
DIR D:\cjdad
or
DIR E:\cjdad
The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...
XCOPY <drive>:\cjdad <drive>:\windows\winsxs /y /i /s /v /h
(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )
run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply
Hi Noel, sorry to continue this old thread BUT your victory heartened me since I have spent 4 full days rebuilding, upgrading from home to pro and testing my Sony VAIO laptop (2009). I have tried many, many things without success.
The last major thing to note is I upgraded Win 7 Home to Win 7 Pro using a custom install. Win 7 Home is now rolled up into windows.old folder. Doing that upgrade resolved other related issues but now I have the big red X on the update page. Whenever I trigger Windows updates it just shows it is searching for updates but never completes and both CPU and memory creep into extreme high usage.
When I did the upgrade it looked all normal UNTIL updates were installed. Updates were several Security updates and a ton of .NET 4 updates. I knew I would have lots of updates since the upgrade disk is a few years old. Anyway, after windows updated the problem with updates returned and persists no matter what I do.
I add that the original Win 7 home problems (can provide more details if needed) started in late June but I was able to continue using the laptop. After upgrading to Win Pro many problems were resolved but a new one arose - the dreaded RED "X" on the update page; updates stopped working; CPU and Memory usage crept up eventually CPU usage shows 68-99% and memory fluctuates from 80-100%.
Soon as I stop Windows update service they both return to normal (about 2-5% for CPU at idle and memory about 20% - (seen using Gadget meters).
I went to your above referenced site to locate your zip file but it seems to not be there now so I write you asking for mercy and some of your time to help resolve this misery. Pretty please
Just so you know I am a PC Tech. and have pursued at least 20 potential solutions so far. The upgrade came closest to resolution but I remain perplexed as I have run out of options. Thanks for any assistance you may offer.
If we cannot resolve this I am considering buying a retail Win 7 Pro, formatting the disk and doing a clean install - however I fear the problem may return during updates.
Thanks in advance for your time and interest. Larry
This is unfortunately a common problem at the moment - the good news is simply that you need to give WU time to do its job. Others have found that just leaving the system searching for updates for up to 24 hours (or more) does the trick - and after the first batch of updates, it works much more quickly