Anyone's computer slow since update?

Ever since i downloaded the 16 windows updates (something like that) a day or 2 ago my computer has been alot slower and having random problems. Sometimes the internet wont play sound but things like skype will, my computer will randomly not read certain songs on cds when i click them in windows media player (discs have no scratches). Has anyone else had any problems?

To check if i had any viruses i did a regular scan and just deleted like 4 tracking cookies. then i scanned my processes with one of nortons features. The 2 things it didnt recognize were

autochk.exe
verclsid.exe

They were created 1-7 days ago and it sayed not many users had those programs and their trustworthiness was unknown.

32bit windows 7 professional

Well, the things I can suggest are

1. Wait a little while and see ifg things improve after the update - they sometimes do
2. defragment your C: drive. Very important first thoguh - run your drive manufacturers diagnostics on the hard drive first to make sure there are not any bad sectors - defragmenting a hard drive with bad sectors will just corrupt more of your data.
3. From a command prompt admin window, run "sfc /verifyonly" to see if there are any system corruption/inconsistencies.

Perhaps there's some connection to the .NET updates that seem to have been released a few days ago.

These ended up causing a low-priority (background) running of MSCORSVW.EXE for a long time, which used up 100% CPU while it was running. True, this is lower priority than anything you normally run in the foreground but it still used all available CPU.

It may or may not be related at all to your own current symptom, but it's worth mentioning.

Please look at this post on that thread, providing instructions to allow NGEN.EXE to complete all of the necessary new compiles for the .NET updates at one time... in the foreground! It will take a few minutes, but once it completes you will not see MSCORSVW.EXE running in the background any longer and using 100% CPU for extended periods.

See if that makes any difference in your situation.

GeneO said:

Well, the things I can suggest are

1. Wait a little while and see ifg things improve after the update - they sometimes do
2. defragment your C: drive. Very important first thoguh - run your drive manufacturers diagnostics on the hard drive first to make sure there are not any bad sectors - defragmenting a hard drive with bad sectors will just corrupt more of your data.
3. From a command prompt admin window, run "sfc /verifyonly" to see if there are any system corruption/inconsistencies.

*i havent tried defragmenting disk yet. i ran #3 first
I ran that and this came up:

Windows resource protection found integrity violations. Details are included in the CBS.Log windir\Logs\CBS\CBS.log.

Integrity violations? I have a legitimate copy of windows and a license for it if thats what it means. What does this mean??

SFC checks the integrity of system files. If a file is corrupted or a protected system file has been overwritten, then it detects this. You can look at the log. If it isn't too big, post here. It may be nothing.

Okay well i ran the sfc/scannow and got this

Windows Resource Protection found corrupt files but was unable to fix some of them.

Details are included in the CBS.Log windir\logs\cbs\cbs.log

I tried to open the cbs file but it wouldnt let me. It said access denied (i am logged into the admin account on my computer. it said i should contact the admin for permission..but i am the admin) .

So what now?

karlsnooks said:

Italia,
You could have harmless problems or serious problems.

Boot into Safe Mode.

once there, navigate to:
\Windows\logs\cbs

Now use DIR to see what's there.
you will see cbs.log and it's size will be monstrous.

To help us separate the wheat from the chaff, I'm going to ask you to delete that file:
DEL CBS.log

Use the EXIT command to get back and now reboot your computer.
Run SFC /SCANNOW once again.

Once again boot into safe mode.

Navigate to \windows\logs\cbs

Execute the following command:
FindStr /c:"[SR]" CBS.log > sfcdetails.txt

Attach sfcdetails.txt to your next post.

I am really sorry, but may I respectfully disagree?

Since this issue has come after updating, if it *is* from the update, we will lose all evidence and any possible chance of analysis if we delete the CBS.log. True, the WindowsUpdate.log will still exist, but CBS.log and WindowsUpdate.log are not the same, and I really don't want to lose such a valuable log (although we may actually be able to recover it from the System Restore Cache via Shadow Explorer)

That command ("FindStr /c:"[SR]" CBS.log > sfcdetails.txt") parses the CBS.log. It only takes a few seconds to do. Just parse the log using that Command without deleting the log file, and all will be well. It only takes about 3 seconds to parse the whole CBS.log on a modern computer.

Also, SFC sections of the log are extremely distinctive, and feature at the bottom of the CBS.log. It is very likely that there will actually only be about 20 lines between the bottom of the log and the SFC log.

Also, I hate parsing the log. Many people don't realise this, but that parsing method loses a vast amount of useful information from the SFC run, and that information saves me a great deal of time when fixing SFC corruptions.

May I please take the whole CBS.log? Do you mind?

Please copy the C:\Windows\Logs\CBS folder to your Desktop, right click on it > Send to > Compressed (zipped) folder, and upload the new file which is created on your Desktop here.

Thanks a lot!

Richard