• Want to test Vista SP1? Anyone can, starting next week
  Mary Jo Foley talks about the SP1 RC release.
  (tags: SP1 RC )
• TechBlog: Windows Vista SP1 Release Candidate goes to testers
  Everyone is saying ‘bits’ now. I noticed it lately on the Windows Vista Team Blog, but now Mary Jo is using it, Dwight is using it, it seems to be all over. Is it the new hip way to talk about downloads? “I’ll just go grab the bits and install them”.
  (tags: Opinion SP1 RC )

Keep reading →

Brandon talks about his experience installing Vista SP1 RC on his 5 PC’s. Keep reading →

• Windows Vista Team Blog : Silicon Valley Install Fair next month
  Another opportunity to install SP1 with Microsoft’s help.
  (tags: SP1 Beta Install )
• Microsoft struggling to convince about Vista
  Yet another survey that says Vista is in trouble in the enterprise. If you ask 1000 people if they are concerned about something, anything, you’re gonna get a large percentage that are. The question is loaded, as are many of these surveys.
  (tags: PR Enterprise Deployment )

Another opportunity to install SP1 with Microsoft’s help. Keep reading →

After you download Adobe Photoshop Elements 6 or Adobe Premiere Elements 4 on Windows Vista, the installer does not start and you can’t find the downloaded file in the folder to which you downloaded it. The Launch button in the Akamai Download Manager window does not do anything.

Consider the following scenario:

• On a Windows Vista-based computer, you try to install an Omniquad Total Security program.
• The Omniquad Total Security program has a product version of 2.0.3.

In this scenario, the installation is unsuccessful. For example, when you try to install TT Firewall 2.0.3, you receive the following error message:

Program Compatibility Assistant
Check online to see if solutions are available from the Microsoft website. If solutions are found, Windows will automatically display a website that lists steps you can take.
Program: TT Firewall
Publisher: Omniquad Ltd
Location: Path of the TSFirewall.exe file
TT Firewall is incompatible with this version of Windows, For more information, contact Omniquad Ltd.

• Why Microsoft must abandon Vista to save itself
  I think I’ve pointed to the ‘VistaSucks’ site before, but if not, you may want to browse it, it’s always good for a laugh. This post seems to suggest Vista sucks because it’s too much like Mac and Linux…
  (tags: Humor )
• Paul Thurrott’s SuperSite for Windows: Inside Windows Vista Service Pack 1
  Lots of info about Vista SP1 Beta.
  (tags: Beta SP1 Review )

Keep reading →

Have Microsoft help you install SP1 Beta on your Vista machine! Keep reading →

On a Windows Vista-based computer, or on a Windows Server code name “Longhorn” -based computer, you install an update package. However, the installation may fail. Additionally, you may also receive the following error message:
Not enough storage is available to process this command.
Note The installation failure occurs if the update package is designed for one of the following operating systems:

• Microsoft Windows 2000
• Windows Server 2003
• Windows XP

When you check the free space on the hard disk, or when you check the physical memory, you find that there is sufficient space to install the package. Therefore, you may find that the error message is misleading.

In Windows Vista, the Package Manager tool can install only the first package when you extract two or more packages to the same folder.

For example, consider the following scenario:

• On a computer that is running Windows Vista, you create a C:\Temp folder.
• You download the following hotfix packages to this folder:
  • Windows6.0-KB929761-x86.msu
  • Windows6.0-KB932590-x86.msu

  These hotfix packages are for hotfix 929761 and hotfix 932590.

• You run the following commands to expand the hotfix packages:
  

  c:\temp>expand c:\temp\Windows6.0-KB929761-x86.msu -F:Windows6.0-KB929761-x86.cab c:\temp
  c:\temp>expand c:\temp\Windows6.0-KB932590-x86.msu -F:Windows6.0-KB932590-x86.cab c:\temp

• You run the following commands to install the packages:
  

  start /w Pkgmgr /ip /m:c:\temp\Windows6.0-KB929761-x86.cab
  start /w Pkgmgr /ip /m:c:\temp\Windows6.0-KB932590-x86.cab

In this scenario, Package Manager installs only the package for hotfix 929761.

When this problem occurs, information that resembles the following may appear in the Cbs.log file:

2007-07-25 13:17:05, Info CBS Pkgmgr: called with: "Pkgmgr /ip /m:c:\temp\Windows6.0-KB932590-x86.cab"
2007-07-25 13:17:05, Info CSI 00000001@2007/7/25:20:17:05.165 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x64ee2e32 @0xf72c09
@0xf6d617 @0xf6dffc @0x772e36ed @0x776fa174)
2007-07-25 13:17:05, Info CBS Session: 29871864:3301734882 initialized.
2007-07-25 13:17:05, Info CBS Pkgmgr: Installing package from: c:\temp\Windows6.0-KB932590-x86.cab
2007-07-25 13:17:05, Info CBS Appl: detect Parent, Package: Package_1_for_KB929761~31bf3856ad364e35~x86~~6.0.1.1, Parent: Microsoft-
Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386, Disposition = 1003, VersionComp: 1, ServiceComp: 1, BuildComp: 1,
DistributionComp: 1, RevisionComp:1, Exist: 1

In this example Cbs.log file, Package Manager indicates that it will install the .cab file for hotfix 932590. However, it actually installs the Package_1_for_KB929761~31bf3856ad364e35~x86~~6.0.1.1 package. This is the hotfix 929761 package.

Note: This problem also applies to Windows Server 2008.