Thursday, December 12, 2013

SVCHOST.exe 100% CPU Usage [XP]

Microsoft may be cancelling support for Windows XP, but that doesn't mean your computer's going to stop secretly checking for updates. Ran into an issue today and one of the things I noticed was that in the Task Manager "svchost.exe" was at 99% usage and staying that way. I thought maybe it was LogMeIn since I was connected remotely, svchost's a network process and upon checking another XP machine, it too had the same redline. Dropping out of LogMeIn and reconnecting showed the CPU usage remained constant.

After a little digging, I saw that this issue can point to Automatic Updates tripping up and the solution is to disable AU. Funny thing is, these are mission critical PCs and thus already have AU disabled... double-checking confirmed that.

By now on the other PC I'd checked, it's svchost.exe was back to normal. From what I read, this issue only affects some PCs. (Obviously, since the internet didn't totally blow up.)

SOLUTION
~

First, make sure Automatic Updates are turned off.

Control Panel -> Automatic Updates


I'm not saying don't do updates - In a business environment it's a good idea to control when updates occur. If you've got a bunch of specialized software, you can lower the chance of random conflicts and errors since you'll be able to draw more cause and effect if a problem creeps up when you can control what software is installed, when.

Identify test users from multiple departments who you can roll updates out to and see how things work. You'll get the best control from configuring your own WSUS server. That's Windows Server Update Services. It allows a domain environment to push updates out yourself, to specific computers, in a user friendly GUI. If your site is bandwidth limited, this is a must as your server will download all the Microsoft updates overnight and domain PCs will grab them locally.

Disable the Automatic Update Service

I've seen updates appear when Automatic Updates were turned off and heard that your computer will still check in to Microsoft from time to time and grab the occasional update. Since I already had Automatic Updates turned off, here's what's fixed it for me.

Control Panel -> Administrative Tools -> Services


Find Automatic Updates in the list and the status will probably already say "Started".

You can select it, then click the little stop button in the menu bar or right-click and choose "Stop" but all that did for me was drop CPU back to normal for a few seconds and back up to 99% with an error that the service can't be stopped right now. The second time I clicked "Stop" it actually stopped and things calmed down.

The sure-fire way is to right-click, choose "Properties" then change the "Startup type" to "Disabled" in the drop-down. This will prevent the service from starting when your computer boots up.

In theory, disabling this service will stop Windows XP from secretly checking for updates.

Friday, June 22, 2012

Leaps of logic [photo]

The leaps of logic people are willing to make when something goes wrong no longer surprises me.

source: Faildesk
I deal with this sort of thing all the time....


Wednesday, June 6, 2012

Transferring Outlook Rules (Cleanly)

"this computer only" was not set on the original computer
Just a simple one here today - have you ever run in to problems with your Outlook rules after transferring a PST from one computer to another?

See, when you create a rule in Outlook, a hidden value in the rule is the computer that the rule was created on, EVEN IF you don't check the option "On this computer only." (That option is more for managing rules in Microsoft Exchange.) This means that even though rules are stored in PST files, if you move a PST to a different computer Outlook will still ignore all your rules and display "(For other computer)" next to them.

Friday, June 1, 2012

The Internet Argument Keyboard?

Biggest CapsLock key ever, or biggest CAPS LOCK key ever?

and that's all I have to say about that...

Wednesday, May 30, 2012

Automating a Backup DHCP Server in Windows Server 2003 and Windows Server 2008

Something that many companies take for granted is their DHCP server. You set one up, and away you go. Even if you really utilize it with reservations, static blocks, extended DNS options, etc... what happens if it crashes? Do you have a backup? Is there an up to date backup with all those reservations and such?

Windows domain computers can still login a few times if your domain controller is unavailable - but they'll still need an IP to get online and perform most of their duties while you deal with why the primary DHCP server is down.

The following discusses creating backups of your Windows Server DHCP server, transferring them to a second server and even automatically enabling the backup if the primary goes down.

Monday, May 14, 2012

Stream multiple computer screens online

The BIG technological hurdle that had to be accomplished for the Headshots from the Heart Marathon was the part that actually turns this into a gaming marathon - we don't want you just watching a webcam feed that shows a bunch of people sitting around playing video games, even with all the extra exciting entertainment and auctions we're going to have going on... we want to bring the action to YOU. We want you to be able to watch us gaming and see every frag we make. In addition to having a webcam that'll show you the hosts and what's going on around us while we play, we're going to be feeding the in-game action DIRECTLY to the stream.

There are a few ways to handle this, and really, it all depends on what exactly you need to setup, and how much money you want to spend.

Just a notice... While I go in-depth in my tutorials, there is a fair amount of stuff here that may be overly technical for some.

Wednesday, May 9, 2012

Modifying a Borderlands save (to reset the critical kill achievement)

For the Headshots from the Heart Marathon, one of the technical hurdles that we needed to overcome was "What happens if someone hits 2500 kills?"

Background:

See, we're taking pledges determined by the number of critical kills we make. Borderlands keeps track of this for us because there's an achievement to reach 2,500 crit-kills. This presents a few problems:

  1. At 2,500 kills, it no longer displays the current count.
  2. Does it keep counting in the background?
    I had a save with well beyond this number, but that was lost last year when a flood blew up my old computer.
  3. Even if it keeps counting and there was a way to access that from the save file, does it max out at some point?
In the following, I'll cover how we plan to deal with this...