...computers: re-register ms-help protocol if deleted by hijackthis (address is not valid)
Add comment April 7th, 2009 at 04:01pm
Add comment April 7th, 2009 at 04:01pm
Add comment April 7th, 2009 at 04:01pm
no sound (dell precision m70, laptops, etc)
http://www.kellys-korner-xp.com/top10faqs.htm #6
http://www.kellys-korner-xp.com/xp_tweaks.htm #371
Add comment April 7th, 2009 at 04:01pm
Can’t connect to winmgmts:{impersonationLevel=impersonate}!\\.\root\default:StdRegProv
stop “windows management instrumentation” service, rename “%windir%\system32\wbem\repository”, start service
http://www.microsoft.com/technet/scriptcenter/topics/help/wmi.mspx#EQKAC
Add comment April 7th, 2009 at 04:01pm
system event logs were set to read only
Add comment April 7th, 2009 at 04:01pm
So continuing with my Visual Studio 2008 installs (and how horrible the installation procedure is), I had a system that ran the Service Pack 1 install and seemed to hang at the end. Normally, I just schedule the install and let it do its thing with unattended setups and an auto-reboot at the end. I got a call from the user saying the SP1 was still installing and this was 5 hours later. I know the SP1 install takes forever, but 5 hours was a little much. So I tried to cancel the install but no luck, so I had to end task SPInstaller.exe.
Off to the log files I go. Wait a minute…the SP1 log file is 5GB! What’s going on?! I wasn’t about to open such a huge file so I deleted all the log files and re-ran the install in non-unattended mode. Shortly after starting the install, it failed with an “Installation suspended, incomplete” message. I thought this meant something but in the end, all it means is that a previous install failed and it rolled some stuff back.
So I ran the install again and this time, it went further, like normal. I noticed on other systems the log file would only grow to 20-30MB so I waited until the log file grew to about 50MB and then end tasked the installer again. I opened up the log file and the end was filled with this message over and over:
Warning 1909. Could not create Shortcut Visual Studio 2008 Command Prompt.lnk. Verify that the destination folder exists and that you can access it.
Why couldn’t it create the shortcut? Who knows? Google, probably. I just searched for “warning 1909″ and saw a bunch of stuff about the Office installer failing with this message. None of the fixes seemed to apply to me. I checked the permissions at C:\Documents and Settings\All Users\Start Menu\Programs and everything seemed good. The VS2008 program folder existed and permissions were also normal.
Well, long story short, this forum thread helped me resolve my issue (I guess this problem also occurs with VS2005). It was on the second page of my search and it’s weird that if I had searched for my message with quotes around certain parts, this result would’ve been hidden by Google.
Anyway, I looked at the system environment variables to see if the ComSpec variable was set incorrectly. And it sure was. It was…missing. Argh, why did the user do that for?! I recreated the ComSpec variable and set it to %SystemRoot%\system32\cmd.exe and re-ran the installer. Everything worked after that. I guess the installer uses that environment variable to determine how to create that command prompt shortcut.
3 comments December 4th, 2008 at 12:28pm
So I’m running the Visual Studio 2008 install on a system the other day and it’s failing. Long story but we’re installing the .NET Framework 2.0 SP1 redistributable first to avoid the automatic reboot with the unattended VS2008 install. So the .NET install runs in unattended mode and near the end, it gives an error:
Error 25015.Failed to install assembly ‘C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.EnterpriseServices.dll’ because of system error: Access is denied.
(more…)
4 comments December 4th, 2008 at 11:58am
Ever since Microsoft began offering Virtual PC for free to download, a lot of users have been installing it to test out the usefulness of virtual machines. A couple laptop users complained that their machines would blue screen while starting up Windows with the wired network cable plugged in, although Windows would start up fine with the cable unplugged (which could then be plugged back in after login). I couldn’t figure it out but did narrow it down to Virtual PC 2004 being installed. I finally had the chance to work on one of these laptops for longer than five minutes and began my search on Google for the answer since I sure couldn’t do it myself. (more…)
2 comments January 5th, 2007 at 03:04pm
Wondering why your Y and Z keys are swapped in X? That’s probably because the keyboard layout is set to German (de) instead of English (us). Did you say you used SUSE AutoYaST and had it configured for the english-us keyboard mapping? Well, we had a couple of AutoYaST configuration files and the layout problem only occurred for a couple of them. I compared the XML files and noticed that in the keyboard section, the ones that didn’t work contained extra settings before the keymap setting (I didn’t make them!). I removed the entries and now the keyboard layout is set correctly! (more…)
Add comment February 16th, 2006 at 03:30pm
Explorer.exe started using 100% CPU about 5 minutes after login. The user had run Spybot, Ad-Aware, and Trend Micro scans and nothing showed up. I took a look at the startup items with msconfig and couldn’t find anything myself. I first ran Process Explorer and couldn’t find anything obvious that was hooked into explorer.exe that would cause the problem (moral of the story: I didn’t know how to use Process Explorer). I ran TCPView and noticed that at login, explorer.exe was trying to connect to an intercage.com IP address (which didn’t respond to pings). As soon as the TCP connection died, explorer.exe CPU usage jumped to 100%. If I end-tasked explorer.exe and re-ran it, it wouldn’t try to make the connection again and it would never use 100% CPU again. If I booted up without a network connection, everything was okay. Once I connected though, explorer.exe would try to make the TCP connection with the mysterious IP again.
After tons and tons of troubleshooting (Filemon, Regmon, SFC, etc.) and searching for solutions (”explorer.exe 100% cpu”, “explorer.exe 99% cpu”, “explorer.exe 90% cpu”, “explorer.exe syn_start”, “explorer.exe close_wait”, “OMG!”), I took a deeper look at Process Explorer’s features. (more…)
35 comments January 12th, 2006 at 04:32pm