Should sfc /scannow fix that? I'll try copying over svchost at some point, and according to the performance monitor, it is certainly a network service that is responsible for the lag spike, mainly UPnP services
2. My prefereed option i have used it in the past is to do an in place upgrade of Windows 7 it is like the old repair install that you could use with Windows XP.
All you need to when you have booted into Windows put the Windows 7 DVD in and choose to install and pick upgrade from the options not custom.
This will replace your Windows folder and rename the current one with .old all service packs and updates will be removed with the .old extension and will need to be downloaded via Windows update again.
You will keep any programs or settings and data you have on the current installation. Just follow the instructions and remove any programs such as ATI catalyst manager and others before doing the upgrade it will prompt you to do so.
Important: Before attempting the in place upgrade to back up your current system and data to an external Hard drive or DVD media before proceeding just in case anything goes wrong or the upgrade does not work as it should.
There may be other things going on in your system that are hard to pinpoint so an in place upgrade may be best.
Right, let's get that SFC error patched up. I am sorry for my delay in replying. It took a little while to source the file. I now have it, and it is 56MB
If you ever get stuck at any point during these instructions, or have any other questions, please stop and ask. I am more than willing to answer questions
Hopefully the file will not be in use, and the problem is the simple thing it should be, and I will be able to fix this the easy way. But if it doesn't, I can always fall back on Plan B. If you have any Text-to-Speech programs open, please
Whilst this is downloading in the background, we need to perform some other steps.
Navigate to C:\Windows\winsxs\amd64_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.1.7600.16385_en-gb_e3a447542ad2c5da\l2057.ngr and copy and paste a backup into a safe place.
Then, going back to the original in the Windows Folder, right click on it and select Properties.
Under the Security tab, click Advanced.
Under the Owner tab, click Edit.
Click "Other Users and Groups".
Click "Find Now".
Scroll down and double click on Everyone.
Click OK THREE times.
Click on the Permissions tab.
Under type Deny, single click on it and click Remove.
Click Edit (now on the standard file Property window under the Security tab).
Click "Find Now".
Scroll down and double click on Everyone.
Single click on Everyone and then tick the "Full Control" box under Allow.
Click OK TWO times.
You should now have permissions to perform the replacement we need. However, it is imperative that at a later stage we reset these permissions and ownership to how they should be. Please stick with me until I give you the go ahead to leave, otherwise your computer's permissions will be left in an unstable state. Please allow me to revert them to how they should be.
Once the download is finished, please extract it into your C:\ drive, creating a file structure of C:\Packs\Windows\winsxs\...
Then open your start menu > search for "cmd" (without the quotation marks) > right click on cmd.exe > Run as Administrator.
Then type the following line and press ENTER:
robocopy C:\Packs C:\ /E /IS
This may take up to 15 minutes to run. Once it has finished, hopefully successfully, please run SFC another twice (once to propagate the replaced file, and reset symbolic links, and once to confirm all has gone well - I do genuinely need two runs - I only tell you to run more than once if it is actually required) and post me a new CBS.log.
Right. As for uTorrent removal, you never install it as such. It's just a single executable that writes a few dirs into your appdata, and nothing else. BUT I do notice a lag spike when I open uTorrent- but my point is this- uTorrent has nothing that runs on startup or any helper applications/services, so IMO removing it will not do anything, because its almost a "stealth" application (as in pretty much portable)
OK, the quick one first. Those instructions were written to be as generic as possible, and apply to all situations, so I can copy and paste them anywhere. There should be no default deny permissions on that part of the Windows folder, although if done correctly, it could work well, and may even be desirable.
Yes, you can. However, I must warn you that there are some serious pitfalls to fall into here, and I would advise caution.
The WinSxS folder, the Trusted Installer, and the Servicing Stack is designed around permissions and ownership. Although it may appear as thought I just gave you any old random instructions to indiscriminately give "Everyone" permissions and ownership, those instructions were actually put together with a lot of careful thought and testing.
I do have a batch file, and indeed a program, to carefully unwind and later re-do permissions and ownership, but I was away from my normal desktop (and indeed still am) and could not easily find it. Therefore, I send you generic manual instructions. That is the honest reason why.
I must warn you, however, not to immediately trust any script on the internet to work here, and I mentioned pitfalls above.
The take ownership script must give ownership to "Everyone", and not your current account. So far, we have only been performing a simple fix, but if things get more complicated, I may need to use special tools. These may run under certain system accounts, or under the trusted installer. It is imperative that you give ownership to "Everyone", so that I know with absolute certainty that any tools I intend to use will work. If we get to a point half way through a fix where one of these tools fails due to ownership, it will all roll back, and I won't necessarily immediately suspect ownership problems to be the cause when I gave instructions which I know have worked countless times before. I would only come to that conclusion after some investigation, and that takes unneeded time. So make sure that you have it set to "Everyone". If you don't know exactly what the scripts does, don't trust it!
Ah, and permissions. I specifically gave instructions which added an additional permission grant to "Everyone". This means that I can easily remove this line and restore permissions to how they were. Many of the scripts online simple set permissions to "Everyone", wiping out what currently exists, rather than adding to what currently exists. This will take longer to patch up when it comes to end cleanup. So please make sure the scripts does that too!
Alternatively, I could give you instructions to miss all of this permissions and ownership stuff out entirely. Do you have a Windows DVD to hand? I can link you to a ~125MB Repair Disk if not. We can then perform an offline fix.
I'm pretty sure I have the repair disk you speak of, but the iso's for the windows 7 dvds are available legally on the internet anyway, so I might just burn one
And also, I did not think they were random instructions Before I installed the take ownership script I did peek into the reg file, and made sure it only does what it is meant to do
I am not able to change permissions of the winsxs subfolders/files, yet I am running on an administrator account, I wish there was a sudo command in windows :lol:
As for the in place upgrade/repair, unfortunately I don't have anything big enough to backup my HDD its 1TB, and almost full, so i'll just have to chance it but I seriously doubt anything will happen. I can just rename the windows.old folder anyway
UPDATE: After a damn 12 hour repair install, it has repaired, and on first try, no service spikes when connecting/dropping the wifi network :lol:
Gonna do a sfc /scannow to make sure everythings ok