Category: Windows Vista

For the last couple of days I have been assisting one the users in my Windows Community alltomxp.se (in Swedish) with troubleshooting the installation of Windows Vista Service Pack 2. The user just get “one or more system components that the service pack requires are missing. For more information, click the link below.”  The links leads unfortunately not to a page with any information on what is wrong.

In the CBS.log the following information can be found:

2009-03-11 20:43:11, Info                  CBS    SPI: Starting SP Compatibility\Applicability scan
2009-03-11 20:43:11, Error                 CBS    SPI: (CSPInstall::CompatibilityApplicabilityScan:993)Detected missing components, aborting SP install hr=0x800f0a0c
2009-03-11 20:43:11, Info                  CBS    SPI: Ending Compatibility\Applicability scan
2009-03-11 20:43:11, Error                 CBS    SPI: (PerformSPInstallation:764)Failed to install SP using UI hr=0x800f0a0c
2009-03-11 20:43:11, Error                 CBS    SPI: (wmain:1034)Failed to perform SP installation hr=0x800f0a0c

The problem is that components are missing, most likely because the application vLite has been used to customize the installation. This can be verified by looking if the registry key HKEY_LOCAL_MACHINE\SOFTWARE\vLite exist and then delete it. After that the installation of Windows Vista Service Pack 2 should proceed, hopefully without further problems.

Recently I have had experience with a customer running Windows Vista on an Apple Macintosh computer. Quite interesting configuration setup and totally unsupported from Microsoft, and to be honest I have never seen so many errors and problems with hardware and drivers as with this machine. Anyway, trying to upgrade BootCamp to the latest version turned out to be a nightmare. Applying the latest BootCamp patch resulted in an instant error message: “Error applying transforms. Verify that the specified transform paths are valid”.

It didn’t take me long to figure out that this was caused by not using a system which is “all-American” but finding out exactly what to change took a bit longer. I soon learned that one have to edit the registry and making sure that the language code set there is changed to the US English code.

You do this by looking up the registry key HKEY_CLASSES_ROOT\Installera\Products \82654E0F812156845A61E8A84572A2CD and then changing the value of the REG_DWORD setting named “Language”. To be able to install Apple BootCamp update this setting must be 0x00000409 (1033).

TechRepublic has written a post on how to Extract troubleshooting info from Windows XP BSOD error messages. This is good, but I must say that extracting even more information from the memory crash dump file is even better. If you’ve missed my guide on how to do this you have it right here:

Troubleshoot and analyze Blue Screens of Death

Microsoft is now announcing some information about Windows Vistas successor with codename “Windows 7”. There wil be no all new kernel in “Windows 7”, instead Microsoft will improve the kernel from Windows Vista and make it more componentized.

Killer compatibility is something that is coming in “Windows 7”, as “all” applications and drivers that work in Windows Vista also will work in “Windows 7” thanks to “Windows 7” being based on the same kernel as Windows Vista. Looking forward to the beta program for “Windows 7”!  

When you install Vista Service Pack 1 the old GPMC.MSC control panel is removed. The reason for this is that there is a new and improved Group Policy management tool released in the Remote Server Administration Tool kit that was released slightly after Service Pack 1 was released to the public.

One of the new features of the new Group Policy management tool is that you can filter policy settings. Directly under “Administrative templates” for both Computer and User Configuration there is a new “All settings” category which lists all settings in “Administrative templates”. If you select “All settings” you might then right click anywhere and choose “Filter options”. It looks like the screenshot below.

By entering the information you are looking for it is very easy to find the group policy settings that you are looking for. This is becoming more and more necessary as the number of policies grows by hundreds or nearly a thousand for every new Windows version released and it is hard to find the setting one is looking for.

Download Remote Server Administration Tools (x86)
Download Remote Server Administration Tools (x64)

This is just a warning to anyone thinking about using Offline files in Windows Vista together with a NAS device. The Offline files feature is activated by default on all folders which you redirect when using Folder Redirection. The problem is that the Offline files feature is not supported by all NAS devices out there.

The Windows Storage Team posted a blog notice about this more than a year ago but this is worth mentioning again. Although they provide a solution for NAS devices using Samba (which many does) there is no guarantee at all that the NAS device has the correct version of Samba or even support making the necessary changes.

Some people for whatever reason want to turn off UAC for all or certain computers in a domain using Group Policies. This is done by setting the Computers Configuration > Windows Settings > Local Policies > Security Options > User Account Control: Run all administrators in Admin Approval Mode to disabled. As usual when turning off UAC a reboot is required for the changes to take effect.

I have had severe problems with System Image Manager crashing when trying to create the Catalog file for a Vista Enterprise SP1 image. The other day an updated version of the Windows Vista Service Pack 1 and Server 2008 Windows Automated Installation Kit was released and my hopes were high for a fix being included. That version crashed as well and after studying the release notes it clearly state that what I am trying to do is no longer supported, as I am running a 64-bit version of Vista and am trying to create a catalog image for a 32-bit image of Vista. Another SP1 problem it seems!

“Because of the changes in the servicing stack in Windows Vista with Service Pack 1 (SP1) and Windows Server 2008, Windows System Image Manager (Windows SIM) cannot create catalog files for some Windows images of different architecture types. The following list describes the Image Manager architecture types and catalogs that can be created for each one.

• x86 Image Manager
  Can create catalogs for x86, x64, and Itanium-based Windows images.
• x64 Image Manager
  Can create catalogs only for x64 Windows images.
• Itanium-based Image Manager
  Can create catalogs only for Itanium-based Windows images.”

See the release notes and download the new WAIK package.

With Windows Vista Service comes a very handy tool which is called VSP1CLN.EXE, short for Vista Service Pack 1 Cleaner. The tool can be found in %SYSTEMROOT%\System32 and when run it makes Windows Vista Service Pack 1 permanent on your computer. In short that means that all files that are backed up during SP1 installation are removed and you will gain several gigabytes of disk space. It also means that you cannot uninstall Service Pack 1 after you have run VSP1CLN.EXE. This tool should pass anyone by!

In Windows Vista it might at a first glance appear to be tricky to automatically enable File and Printer sharing and Network discovery. However it is actually very easy when you know what to type. The “netsh” command comes in handy here, and you can use the below strings in a script to enable it on many clients automatically.

To enable File and Printer sharing you run the command:

netsh firewall set service type=fileandprint mode=enable profile=all

To enable Network discovery you run the command:

netsh advfirewall firewall set rule group=”network discovery” new enable=yes

Please note that you can change which profile you want to apply the changes for.

EDIT: First and foremost, I accidently added the “profile=all” to the Network Discovery string which is totally incorrect, as Network discovery is enabled for all profiles when this command is run. Second, if you are using Windows in another language than English you will have to adjust “network discovery” to what it is called in your localized language. For instance on the Swedish version of Vista it would be:

netsh advfirewall firewall set rule group=”nätverksidentifiering” new enable=yes

EDIT 2: The network discovery script only work with Windows Vista with Service Pack 1.