Vista Sleep Problems

Vista on my Fragbox2 PC has a problem with sleep mode. When I click the Start > "Power button", it works for a couple of seconds; then I hear a "click" and HD and most of the PC shutsdown but fan keeps on running.

I could not remember if I had updated the firmware on it since I bought it last year but I suspected my Asus P5E-VM DO had something to do with this. Unfortunately, I failed to find anything on Asus forums.

Today, I was trying to locate what key was causing PowerDVD registration reminder to pop-up via Sysinternal Procmon and noticed that my Philips camcorder was constantly querying registry. I decided to disable it.

So, I ran Start > msconfig and while there started to clean up other unnecessary stuff like pesky Adobe Acrobat's acrobat_sl.exe.

That's when I looked closer at two Logitech start-up processes:

• SetPoint.exe
• KHALMNPR.exe

I knew that they belong to my Logitech G7 software; the only reason I had installed them was to dynamically increase/decrease sensitivity while playing World of Warcraft. As I quit playing it; there was no reason to keep the software. I checked the forums anyway and found out that someone else was complaining about Vista not going to sleep mode with these running.

I disabled them and rebooted. It worked. Vista sleeps happily now :)

Update:

Well, it was not happily ever after :(

I did solve the problem for good though:

Apparently there are two Sleep levels in BIOS; S1 and S3 ( dont know what happened to S2). So, I had to go into BIOS and change sleep level to let it go to 'deep sleep'.

Vista Post-SP2 Black Screen. Is Vista slower?

There are tons of XP vs. Vista posts on web. To be honest, I have a pretty fast PC and never I could care less if Vista is a couple of seconds slower than XP; it's still fast. This post is not looking to make a comparison but it is more about a couple of useful things I discovered when I was looking around post-sp2 upgrade. Here is what happened...

Post-SP2 Black Screen

I've downloaded and installed Vista SP2 on one of my laptops and noticed that there was an extended period of "black" screen during boot time. I did not pay much attention to it but today I noticed the same thing on my desktop post SP2.

Vista Logs

It tickled my curiosity and I started looking around. Soon, I found out that Vista Logs are incredibly detailed and there is abundant information to diagnose such stuff. That is great news because I always hated XP's inability to tell me what was causing slowness during boot. I would sit there and watch for 4-5 mins painfully while my laptop crawls to a start. Of course I tried invaluable Sysinternal tools like Procmon to watch boot process and try to sift thru hundreds of thousands of records which was mostly useless...

So, first I headed to Control Panel to see what was Vista reporting recently:

Control Panel > Performance Information and Tools > Advanced Tools

I have not seen anything in the recent "Performance Issues" section that suggested that I was seeing a degradation of system boot but interestingly enough there was some clue to another issue I was seeing on my Pc recently; it just would not go to Sleep mode...

You will notice that at the bottom of the dialog box; there is a link to the Event Viewer; and that's the beauty of Vista. This basically means that Vista is in fact going thru performance logs and giving you a summary of recent events...

Diagnostics-Performance

To get to Diagnostics-Performance logs, you can click the link above or open up Event Viewer

Start > run > eventvwr.msc then browse to

Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational

Under the Operational, you will see tons of events logged. There a couple of Task Categories.

• Click on "Task Category" and
• Select "Group Events by This Category"

From category names, it's clear that "Boot Performance Monitoring" is the one that should give us the information we are looking for.

In the screenshot above you will notice that; Vista is in fact telling us about the time it took to boot. There is more, if you click the details tab, there is actually a breakdown of boot time! I think this is a very neat feature b/c I still remember how painful it was for me to use a stopwatch to record each phase of XP boot visually and then try to match them to whatever was recorded by extended Group Policy logs and Event Logs... It's all there; in the event logs now.

When I looked at break-down of boot times, it was not easy to tell what some of them were; so I googled and in fact found an article titled "Microsoft's hidden diagnostic tool unlocks Vista startup secrets". Well, there is not much there other than what I had already found out but it mentioned two parts of boot time:

MainPathBootTime measures the time it takes for the system to load all drivers and services that are critical to user interaction and get to the Windows desktop where the user can begin doing things.

BootPostBootTime includes all the other drivers and processes that aren’t critical to user interaction and can be loaded with low-priority I/O that always gives preference to user-initiated actions that execute using Normal I/O priority.

I tried to find the follow up writing on ZD net but after spending 20mins to no avail; I gave up.

I filtered by Event ID 100-190:

• On the left pane, right click on "Operational"
• Click "Filter Current Log"
• Replace "" with 100-190

And started to look at boot times. Apparently my boot up time was around 80000milliseconds (ie. 80 seconds) but the latest boot time was a whopping 262sec (4.3mins). Unfortunately, there was no smoking gun; and Windows did not report anything unusual in this case.

This may be OK though; because I remembered that I had also installed Office 2007 SP2 and had not rebooted yet; so this might have been the cause of delay. To be sure, I will need to reboot a couple of times and measure them to see if I was still getting 80secs.

During the investigation, I noticed that at times, some apps (McAfee Antivirus, Rawr etc) were causing delays and Windows were reporting such events. By the way, the same log is also used to determine what is blocking a machine from sleeping or causing delays during shutdown.

Conclusion

So, is Vista slower than XP? Maybe but I don't care. With XP, I could never tell what was causing slowness. Now, at least I have better visibility. Overall, I like Vista more.

Vista Tweaks

I just encountered a forum entry that talks about tweaking Vista and has an extensive list. Some of them really useless crap in my opinion but there are lots of interesting and useful tweaks also... Eg. Activate hidden admin account by typing
net user administrator activate:yes
or
net user administrator "your pwd" activate:yes
Take a look!

Vista - Cannot Open Control Panel (Fixed)

World of Warcraft was giving me headache yesterday. FPS near Ogri'la was only 4fps, although lag was not too bad (~150-200ms). So I decided to disable addons, defrag HD blah blah. I was also using procmon from sysinternals to see if there was anything hogging Vista...

I noticed SearchIndexer was a bit troublesome and stopped the service. While there, I went thru the list and disabled a couple of other that did not seem useful/applicable. One of them was "Software Licensing".

Software Licensing Service Description:
Enables the download, installation and enforcement of digital licenses for Windows and Windows applications. If the service is disabled, the operating system and licensed applications may run in a reduced function mode.

Apparently, if you disable this service you cannot open Control Panel. It looks like it's coming up but then disappears immediately. Enabling/starting service fixes the issue...

Vista - Still Bluescreens

After installing Vista SP1 RC1 and moving Page file to a different hard drive, I was finally not able to get rid of BSODs when computer was idle...

After a coupel of weeks, unfortunately freezes and BSODs came back. The last one I had said something like:

Win32k.sys

Page_Fault_In_Nonpaged_Area
STOP 0x00000050 (0xFFC000000,all zeros,0x964E0FB3, All Zeros)...

Apparently, Microsoft has a hotfix for this. There is an article titled "Error message when you start a Windows Vista-based computer: "STOP: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA" ( http://support.microsoft.com/kb/939720 )

However, this article mentioned issues during startup, which was not really my case. I kept on looking and found another KB article: http://support.microsoft.com/kb/939720 about STOP: 0x00000050.

From http://support.microsoft.com/kb/244617 I get the feeling that one of the drivers is not playing well with vista. I ran c:\windows\system32\verifier.exe to see if it will be able to help me pinpoint the issue.

Windows Vista SP1 RC1 Issues

One of my computer is locking up almost every day. I leave it alone at night, when I come back in the morning I see it BlueScreened. I googled "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR" and tried to find something that would explain my BSOD with Vista to no avail... and decided to try Vista SP1 RC1.

I downloaded the stand-alone version and tried to install it. It bluescreened half way there after half an hour or so (well, it said SP1 update can take hours in the screen so half an hour is great).

I tried on my other Vista machine and it even did not get that far. Then, Microsoft refreshed RC1 and I decided to try it again as my Vista keeps on locking up.

So, I browsed to Windows Vista Service Pack 1 page, and downloaded Windows Vista SP1 RC Refresh (Build 17128) – released 01/11/08. When unpacked it has 3 files in it. I ran the cmd, which entered a registry key that enabled me to see an Update for Vista SP1 Control Panel > Windows Update > "Check for Updates".

Update actually installed 3 files, rebooted. Then I went back to Windows Update and clicked "Check for Updates" but it did not find anything. I waited and tried a couple of mins later. This time it finally found SP1 RC1. I clicked install and it froze on me after a few mins.

I tried a couple more times suspecting that whatever issue was causing my lock-up , it was preventing update from finishing. And Windows Update was able to finish the download but it failed to install it. Error code: 80070005. Unfortunately Vista help did not list this error code.

After some search, I realized that many other has seen the same issue and the only solution I saw was Aaron Stebner's blog entry. Apparently, MS messed up permissioning and Windows Update does not have enough permissions to write some reg keys/files.

I followed the instructions mentioned. I do not know if this will work for me yet. I will post a follow up later.

[Update - 01/21/2008]
I ran the script from Aaron's page. It did a lot of things but failed to reset permissions on 7 keys. I rebooted and tried again, it kept on failing. I also tried running SP1 update but it too failed...

I looked into the error Kernel_Data_InPage_Error, I was getting. I had the following error codes: 0000007A (0xC020BF84, 0xC00009C, 02a266860, 0x82FE130D)
ntfs.sys - Address 82FE130D base at 82EF8000 Datestamp 47214597

So, there are 4 block of error codes:
1st set is about Lock Type (0xC020BF84)
2nd set is the I/O status (0xC00009C)
3rd set tells us about Current Process when BSOD occured(02a266860)
and 4th set mentions the memory code where error occured.

As per this article at MSDN, my issue was 0xC000009C, or STATUS_DEVICE_DATA_ERROR, is typically due to bad blocks (sectors) on the hard disk.

As my Page File was in C drive, probably there was some bad blocks in the C drive. Unfortunately, chkdisk did not help. So, I moved the page file to my other drive.

No lockups since then. And to my surprise, Vista SP1 RC1 installed successfully today!

Vista BSOD

My vista install started to crash when there is a lot of disk activity. It would crash every other day at first. Then, at some point it started to go down shortly after I initiate PowerUsenet downloads.

I looked at MS documentation for 0x0000007B and concluded that it had something to do with Sata controller. Article suggested to replace cables as it could be caused by a faulty cable but doing so did not help.

Then, I bought a HighPoint Tech TocketRaid 1742 PCI card. Documentation suggested to simply install the card and point to the driver location once Vista detected it. Unfortunately, Vista kept on blue screening once card was installed and I could not reach the logon page.

I installed the card on an empty PCI slot and connected back my Promise SATA controller. After the Vista came up I installed drivers, shutdown pc and removed the promise controller. Then, I reconnected my SATA HDs to the new controller and succesfully booted.

I hope this will end my BSOD issues....Time will show.

A (much needed) update for Vista

Today, when I saw MS KB938194 titled "An update is available that improves the compatibility and reliability of Windows Vista" and look at the issues it resolved, it reminded me of my experience with an ATI card when I moved to Vista:

A couple of months ago I bought a nice (=expensive) ATI all in wonder X800 video card and it worked perfectly fine under Windows XP when I was playing World of Warcraft (WoW). Then, I installed Vista. All seemed fine for a week or so and then hell broke loose...

At first, I would not be able to play more WoW than 5 minutes. It would freeze and I had to reboot. Then it got worse so that I could not even play 30 secs. I gave up and started to use my other PC to play the game.

It got even worse when Vista started to freeze even when I am not playing a game but just playing any video file. At some point, my pc was totally unusable as animations were too much to display.

One of these days, I saw a sign that CompUSA shop near my house was getting closing and there was a close-out sale. I bought ATI X1600 Pro & retired the problematic one but promised myself to test it out on my Windows XP box to see if the problem would present itself there too...

Read this article for more on Windows Vista issues and possible fixes coming out...

Vista UAC is just trouble

I am sorry to say this but Vista UAC is broken! I understand the concept, and I understand where Microsoft is coming from. In fact, I felt quite comfortable the way Ubuntu has implemented basically the same idea. But it is just painful in Vista.

I tried to work with it but got fed up soon. So, I disabled it using Local Group Policy. And then, my problems started. I did not realize it until today but UAC was the reason behind a couple of mysterious issues I was having. A few recent examples...

* NTFS permissions are all screwed up. Although my user account is in Administrators/backup operators groups, I sometimes can not access my personal folders. Then, I have actually blogged this here, so I wont go into details...

* My backup process got broken. I loved rsync in unix world and the closest thing I have in Vista is of course good old Robocopy. I already had some backup scripts that would take daily back ups between my various disks and PCs. Time to time, I would get mysterious errors like "ERROR 5 (0x00000005) Changing File Attributes"...

* Windows update would never install 'any' update. It kept on downloading the files and then reported errors but never offered any explanation why.

Finally, I suspected that UAC was not fully disabled. I saw a nicely written article and used msconfig method (Run msconfig > Tools > Disable UAC).

And guess what? Suddenly all looks good now :)

Vista fails to boot

My vista ultimate crushed today for no apparent reason. As if that's not bad enough, Vista could not be loaded. Instead, I was stuck at the screen.

*******************************
WINDOWS BOOT MANAGER
Windows failed to start. A recent hardware or software change might be the cause. To Fix the problem:

1. Insert your Windows installation disc and restart your computer
2. Choose your language settings, and then click "Next"
3. Click "Repair your computer"

If you do not have this disc, contact your system administrator or computer manufacturer for assistance.

File: \Windows\system32\winload.exe

Status: 0x000000e

Info: The selected entry could not be loaded because the application is missing or corrupt
*******************************

Resolution: Simple, I simply unplugged the exterior Sony DVD burner. A funny fact was that simple reboot did not fix the issue but I shutdown the PC completely and then powered it on.

Vista snipping tool error

I had an interesting issue with my Vista build today. Well, I have to disclose that this is basically a preview build that our engineering team is testing in the company. I was trying to launch Snipping Tool and received an error:

The Snipping Tool is not working on your computer right now. Restart your computer, and then try again. If the problem persists, contact your system administrator.

Sure enough, rebooting the machine did not help. I checked the event viewer and noticed that a warning gets logged everytime I try to start it:

Log Name: Application
Source: Microsoft-Windows-SoftwareRestrictionPolicies
Date: 7/12/2007 3:15:25 PM
Event ID: 866
Description:
Access to C:\Windows\SYSTEM32\WISPTIS.EXE has been restricted by your Administrator by location with policy rule {F8509577-AE57-4057-B256-2929FCC0931A} placed on path *WISPTIS.exe.

So, what's this Wisptis? "Windows Ink Services Platform Tablet Input Subsystem".
I ran rsop.msc to confirm that it was listed under

"Computer Configuration" > "Windows Settings" > "Security Settings" > "Software Restriction Policies" > "Additional Rules"

Why would snipping tool need Wisptis.exe is beyond me.

[Edit: 04/04/2008]
I've scraped the preview build long time ago and I use ultimate version for sometime. However, I get comment from people who still see the issue I mentioned above. I got two comments from people who confirmed that running "Office Diagnostics", however irrelevant it seems, fixed the issue for them.

It makes me very happy to see comments from people who reach this blog and either find or suggest solutions to problems. Thank you all!

Vista Auto Logon

According to: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=829701&SiteID=1 If you have a single user without password, then he gets logged on automatically after restart.
Not recommended! Of course, anyone with sufficient access to read your registry, can read your password in plain text if you set it up this way…

Here’s the procedure:
Open Regedit,

• Drill down to HKLM/Software/Microsoft/Windows NT/CurrentVersion/Winlogon,
• Find the “AutoAdminLogon” value, and change it to 1. Enter the following items as new string values: “DefaultUserName”, and “DefaultPassword”.
• Set the value of DefaultUserName to be the username that you want to autologin, and set the value of DefaultPassword to be that user’s password.

Vista Documentation & Tools

Microsoft has a lot of good reading material for IT Professional on their site about Vista. They have also released a few useful tools:

SyncToy v1.4

SyncToy helps you copy, move, rename, and delete files between folders and computers quickly and easily.

Group Policy Log View

This page provides the Group Policy Log view tool for Windows Vista

Windows User State Migration Tool (USMT) version 3.0

Microsoft® Windows® User State Migration Tool (USMT) version 3.0 migrates user files and settings during deployments of Microsoft Windows XP and Windows Vista™. USMT captures files and settings from the source computer and then migrates them to a new Windows installation.

Windows AIK

The Windows Automated Installation Kit (Windows AIK) helps you to install, customize, and deploy the Microsoft Windows Vista™ family of operating systems.

Remote Desktop Connection (Terminal Services Client 6.0) for Windows XP (KB925876)

Remote Desktop Connection (Terminal Services Client 6.0) provides a way to use any new Terminal Services features introduced in Microsoft Windows Vista and Microsoft Windows Server Code Name “Longhorn” from a computer running Microsoft Windows XP with Service Pack 2 or Microsoft Windows Server 2003 with Service Pack 1.

Consolas Font Pack

The Microsoft Consolas Font Family is a set of highly legible fonts designed for ClearType. It is intended for use in programming environments and other circumstances where a monospaced
font is specified. This installation package will set the default font for Visual Studio to Consolas.

and even more documentation on Security:

Windows Vista Security Guide

The Windows Vista Security Guide provides recommendations and tools to further harden Windows Vista. Use the GPOAccelerator tool in this Solution Accelerator to efficiently establish the Enterprise Client (EC) environment or the Specialized Security – Limited Functionality (SSLF) environment.

What about Users? Well, they can take a look at this:

Windows Vista User Experience Guidelines

Download a preliminary draft of the Windows Vista™ User Experience Guidelines (UX Guide).

and Best Practices?

Power Management for Windows Vista Best Practices

Use computer power plans to reduce consumption with Windows Vista.

Everyday Work with Windows Vista Best Practices

Work smarter with new features in Windows Vista.

Enjoy!

PowerDVD Issue with Vista Aero

I use Cyberlink PowerDVD 7.0. Everytime I started it up, Vista would pop up an message saying that PowerDVD would not support Aero and therefore Aero features (transparency etc. ) would be DISABLED. I see screen flickering and then PowerDVD starts. As soon as I shutdown PowerDVD, I see screen flickering again and Aero is back!

Well, good news is that Cyberlink has an updated build (#2211) for PowerDVD that you can download for free & it resolves this issue.

Vista Aero at last!

When I installed Vista, I was disappointed to see that my Windows Experience Index was 1.0 I was disappointed because I have a pretty decent machine:

• HP XW6000 Workstation
• 2 x 2.8 GHz P4 processor
• 1 GB DDR 266Mhz RAM
• 2 x 750GB SATA drives
• nVidia 980XGL video card with 128 MB ram & dual DVI output
  

So, what was wrong in this picture? Why was I getting such a bad score? Well, apparently, Windows Experience Index base score is determined by the lowest number. And what was that? Yep, you probably guesses it right. It was my video card.

It looks like I fell behind times in video cards department and I felt that this was a good time to catch up. So, I did some research. As always, Tom's Hardware Guide on graphic cards was pretty useful.

I ended up ordering an AGP 8x, ATI Radeon GDDR3 X800 XT with 256 MB ram from TigerDirect.com for $168 (I checked again now and they are not selling it anymore, maybe I got the last one :). It's all-in-one card, although I am not currently planning to use its TV capture capabilities.

I received in just two days. When I installed it though, my machine did not boot, all I was hearing was 2 long beeps. I put back the old card and got on internet to talk to HP. They simply told me that
- "ATI Radeon X800 XT card is not tested on xw6000 and is not supported".

In fact, HP guy told me that there was a problem between it and the motherboard but I kept on asking questions and he confessed that he was not sure of that and suggested I try the *newest* BIOS which was 2 years old and I was already running that.

I started tinkering with BIOS settings and one setting got my eye "AGP Aperture Size". It was set to 64MB. I did not know what it was for but when I saw someone mentioning it to fix a video card issue (not ATI), I realized that I had to change it to 256MB = what my new card had & voila!

To my surprise, Vista detected the card and installed the driver for it. Then, I checked my Windows Experience Index again: 4.3

This time, it was my 1Gig memory that was taking me down but hey, I have all the bells and whistles of Aero now :) I am quite disappointed with Doom 3 though, it looks better but not way better...

BTW, to see your Windows Experience index, do the followings:
Start > Run
control.exe system

Lastly, I wrote about BlackBerry on Vista yesterday. I checked the device in the morning and as expected it was fully charged.

Blackberry & Vista

when I connected my Blackberry 8700 to Vista to charge it, it immediately popped up a message telling me that "a blackberry device was found". It did not however had the software for it

I checked the device manager and sure enough BlackBerry was listed with a yellow icon on it meaning that it was missing the driver.

I went to RIM's homepage to see if they had any Vista drivers but could not locate one.

As my experience with Vista so far showed me that XP drivers usually worked fine, I wanted to give it a try by downloading and installing the latest BlackBerry Desktop Software (4.2 as of this moment).

So I downloaded the software and installed it. Installation went just fine no issues. I have selected Enterprise features as mine is in fact belongs to my company.

As I only wanted to charge the battery and I selected not to launch the application at start up. I will probably not be able to use it anyway. Still, when I launched it, it came up just fine.



Then, I went back to Device manager to see what happened and noticed that it was now showing under Universal Serial Bus Controller. Right now, it looks like it is charging. I will check back in the morning to see if it 'really' charged.

Vista - Change Explorer Start up Directory

In Vista, Windows Explorer is located under All Programs > Accessories. It's actually a shortcut to%SystemRoot%\explorer.exe

When you open it, by default it will open your "Username"\"Documents" Folder:

I do not want that! Instead, I want it to show me the root of my D: drive. Well, it's not difficult to change. Here is how:

• Create a shortcut to Windows Explorer:

1. Go to All programs > Accessories.
2. Right click "Windows Explorer"
3. From menu choose "Send to" > Desktop (Create Shortcut)

• Then right click on the new shortcut and from the menu choose properties
• Modify "target" by adding /root,D:
• It should now appear like this: %SystemRoot%\explorer.exe /root,D:

That's it. From now on, when you open Windows Explorer using that shortcut, it will go to the root of D: drive. This is actually and old trick and works well with Windows XP too.

[Update - 12/03/2006]

I made a mistake above. If you want do NOT want to see other drives when you start up and just D drive, then instructions stand. Otherwise, just modify target like this:

• %SystemRoot%\explorer.exe D:

Vista: Corrupted Recycle Bin

One of the issues I see everyday with Vista is about the recycle bin. It keeps on getting corrupted. I suspect that this is because of my dual-boot configuration with XP and may be permissions. It does not matter how many times I click "YES", it keeps on popping up. I am not sure how to fix it yet and the weird thing is that there is nothing in the eventlogs!

Vista ReadyBoost & ReadyDrive

Jim Allchin, has an informative article on a new feature in Vista: ReadyBoost. Below is an excerpt from this article.

... With Windows ReadyBoost, if you have a flash drive (like a USB thumb drive or an SD card) you can just use this to make your computer run better with Windows Vista. You simply plug in a flash drive and Windows Vista will use Windows ReadyBoost to utilize the flash memory to improve performance.

I should be clear that while flash drives do contain memory, Windows ReadyBoost isn’t really using that memory to increase the main system RAM in your computer. Instead, ReadyBoost uses the flash drive to store information that is being used by the memory manager. If you are running a lot of applications on a system that has limited memory, Windows ReadyBoost will use the flash drive to create a copy of virtual memory that is not quite as fast as RAM, but a whole lot faster than going to the hard disk. What is very cool here is that there is nothing stored on this flash disk that isn’t also on the hard disk, so if you remove the flash drive, the memory manager sees the change and automatically goes to the hard disk...

Unfortunately for me, my Corsair USB 2 drive did not qualify :( This is a bit surprising. I am not sure what qualification is considered adequate by Vista...


There are some articles on microsoft site that talk about ReadyBoost but they do not mention specifics.

As USB drives are very common these days, I think Microsoft had the right idea. Vista also supports Hybrid drives (HHD = regular HD + integrated NVRAM) via a technology called ReadyDrive.

These are welcome changes. What I understand from Allchin's message though is that Vista does not perform considerably better compared XP if you do not have a high-end system, which is a bit disappointing. Would not it be nice to see a lightning fast OS after so many years of development.

[Update - 12/05/2006]
On the comment section, somebody left me a message with a link to Tom Archer's blog. The link was not working but I was able to read the article when I hit the home page of the blog.

I am not sure what is the problem with my USB stick even after reading some of the requirements as it they did not mention a tool to measure the specs of usb stick but a few people suggested that they got their usb stick working when they formatted it with ntfs.

There was a link to another useful article at DvNation. Check it out.