If you use a network trace when this problem occurs, the network trace may indicate that the WebDAV server generates a code 401 (Authorization Required) error.

Back to the top

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, 32-bit editions

Windows Vista, 64-bit editions

Back to the top

Back to the top

Back to the top

• Exchange database online maintenance
• Information Store (IS) maintenance
• Quota notification
• Offline Address Book (OAB) generation

This issue occurs if Exchange servers are configured for time zones that observe daylight saving time (DST).

This behavior is by design.

Administrators must configure these schedules to accommodate for DST changes that occur in the time zones in which the Exchange servers are located.

Log Name: Application
Source: .NET Runtime
Event ID: 1023

.NET Runtime version 2.0.50727.3053 – Fatal Execution Engine Error (000007FEF671203F) (0)

Back to the top

In this scenario, System.Core.dll is reuqested by Microsoft.PowerCommands.dll. In certain scenarios, System.Core.dll loses its native image and is loaded in the wrong context, which results in the crash.

Back to the top

1. Using Notepad, open the devenv.exe.config file which is situated under Program Files Visual Studio 9 Common7 IDE folder.
2. Locate the <assemblyBinding> element underneath the <runtime> element. You should see a number of <dependentAssembly> elements listed under this.
3. Add the following <dependentAssembly> entry at the bottom of the <dependentAssembly> entries.

<dependentAssembly>
   <assemblyIdentity name=Microsoft.PowerCommands publicKeyToken=null culture=neutral/>
   <codeBase version=1.1.0.0 href=C: Program Files PowerCommands Microsoft.PowerCommands.dll/>
</dependentAssembly>

4. Be sure to place the path to Microsoft.PowerCommands.dll with the path to it on your computer.
5. Save the file and close it.
6. Restart Visual Studio 2008.

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Error message 1

Error message 2

Back to the top

To resolve this issue, follow these steps on the first computer:

1.	Click Start , and then type policy in the Start Search box.
2.	Right-click Local Security Policy, and then click Run as administrator.
3.	Expand Local Policies.
4.	Click Security Options.
5.	In the Policy list, double-click Network Access: Named Pipes that can be accessed anonymously.
6.	On the Local Policy Setting tab, type the name of the second computer. This is the Server2_name name in the error message that you received.
7.	Click OK.
8.	Double-click Network access: Let Everyone permissions apply to anonymous users.
9.	Click Enabled, and then click OK.

Back to the top

Windows Vista lets anonymous users perform certain activities, such as enumerating the names of domain accounts and the names of network shares. For example, Windows Vista lets an administrator grant access to users in a trusted domain that does not maintain a reciprocal trust. By default, the Everyone security identifier (SID) is removed from the token that is created for anonymous connections. Therefore, permissions that are granted to the Everyone group do not apply to anonymous users. Anonymous users may access only those resources for which the anonymous user has been explicitly granted permissions.

By default, the Network access: Named pipes that can be accessed anonymously policy setting is None. This security setting determines whether named pipes have attributes and permissions that enable anonymous access. If the Network access: Named pipes that can be accessed anonymously policy is enabled, the Everyone SID is added to the token that is created for anonymous connections. In this case, an anonymous user may access any resource for which the Everyone group has been granted permissions.

Back to the top

Back to the top

Back to the top

Back to the top

Note User Account Control (UAC) is a new feature that helps prevent malicious programs, also known as malware, from damaging a system. UAC stops the automatic installation of unauthorized applications. It also prevents unintended changes to system settings. Before you disable UAC, you must disconnect your computer from all networks. This includes the Internet.

To work around this issue, follow these steps:

1.	Log on to Windows Vista as a user who has administrator rights and permissions.
2.	Click Start , and then click Control Panel.
3.	Click User Accounts and Family Safety, click User Accounts, and then click Turn User Account Control on or off. Note In some versions of Windows Vista, User Accounts and Family Safety does not appear. In this case, click User Accounts, click User Accounts, and then click Turn User Account Control on or off. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
4.	Click to clear the Use User Account Control (UAC) to help protect your computer check box.
5.	Click OK.
6.	When you are prompted, restart the computer.
7.	Right-click the public folder that you want to move, and then click Properties.
8.	On the Location tab, click Move.
9.	Select the new location, and then click Select Folder.
10.	Click OK.
11.	Click Start , and then click Control Panel.
12.	Click User Accounts and Family Safety, click User Accounts, and then click Turn User Account Control on or off. Note In some versions of Windows Vista, User Accounts and Family Safety does not appear. In this case, click User Accounts, click User Accounts, and then click Turn User Account Control on or off. If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
13.	Click to select the Use User Account Control (UAC) to help protect your computer check box.
14.	Click OK.
15.	When you are prompted, restart the computer.

Back to the top

In this scenario, a blank clip art image is inserted in the Works Word Processor document.

Back to the top

For more information about the Works 8.5 security update, visit the following Microsoft Web site:

Back to the top

Note When you insert clip art in a Works Word Processor document in Works 8.0, the clip art collection appears. You can then select and insert the clip art image that you want.

Back to the top

Back to the top

Back to the top

•	Windows Boot Manager Set this entry to point to the system partition. To do this, follow these steps: 1. Click Start , click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type your password or click Continue. 2. At the command prompt, type bcdedit -set {bootmgr} device partition=S: Note In this command, S: represents the drive letter for the system partition.
•	Windows Memory Tester Set this entry to point to the system partition. To do this, type the following command at the elevated command prompt: bcdedit -set {memdiag} device partition=S: Note In this command, S: represents the drive letter for the system partition.
•	Resume from Hibernate Set this entry to point to the operating system partition. This partition is also known as the boot partition. To do this, follow these steps: 1. At the elevated command prompt, type bcdedit -enum all. Note the identifier value for the Resume from Hibernate entry. 2. At the elevated command prompt, type bcdedit -set {identifier} device partition=C:. Note In this command, identifier represents the identifier value for the Resume from Hibernate entry in step 1 of this procedure. Also, C: represents the drive letter for the boot partition.

Back to the top

Back to the top

Back to the top

If you click Yes in the message, the meeting page closes and saves the meeting. However, Outlook does not send out meeting cancellations to the attendees.

Back to the top

Back to the top

Back to the top

Method 1

Cancel the meeting without saving it in the organizer’s Calendar folder. To do this, follow these steps:

1.	Open the meeting in the organizer’s Calendar folder.
2.	On the Recurring Meeting tab, click Cancel Meeting in the Actions group. This sends meeting cancellations to the attendees and removes the meeting from organizer’s Calendar folder.

Back to the top

Method 2

Remove attendees from the meeting, but save the meeting in organizer’s Calendar folder. To do this, follow these steps:

1.	Open the meeting in the organizer’s Calendar folder.
2.	On the Recurring Meeting tab, click Scheduling Assistant in the Show group. This opens a page that has a list of all the attendees and the organizer.
3.	Under All Attendees, click to clear the check boxes next to all the attendees.
4.	Click Send. Meeting cancellations will be sent to all attendees. Also, the organizer can save this meeting in the Calendar folder.

Back to the top

Back to the top

Back to the top

Back to the top

When hovering the mouse over a Node in the TreeView control, the ToolTip may not display all the text specified in the SetToolTip method. When exiting the application, you may also receive the following error:

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at System.Environment.GetResourceFromDefault(String key)
   at System.ObjectDisposedException..ctor(String objectName)
   at System.Windows.Forms.Control.DestroyHandle()
   at System.Windows.Forms.Control.Dispose(Boolean disposing)
   at System.Windows.Forms.Form.Dispose(Boolean disposing)
   at WindowsFormsApplication1.Form1.Dispose(Boolean disposing) in C: Projects WindowsFormsApplication1 WindowsFormsApplication1 Form1.Designer.cs:line 20
   at System.ComponentModel.Component.Dispose()
   at System.Windows.Forms.Form.WmClose(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

If you are debugging the application in Visual Studio, you may receive the following MDA error when exiting instead of the System.AccessViolationException above. 

FatalExecutionEngineError was detected

The runtime has encountered a fatal error. The address of the error was at <address>, on thread <thread>. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.

Back to the top

Back to the top

You can use one of the following solutions to work around this problem.

1. Set the TreeView control’s ShowNodeToolTips property to False. This is the easiest solution if the intent is to use the ToolTip control for displaying ToolTips instead of the TreeView control’s built-in Node ToolTips (the ToolTip control has some additional features not exposed by the TreeView control’s ToolTip implementation).

2. Alternatively, you can remove the call to the ToolTip control’s SetToolTip method, and use the TreeView control’s built-in ToolTips. To do this, you must make sure that the TreeView control’s ShowNodeToolTips property is set to True, and that you have set each TreeNode’s ToolTipText property to the desired value.

Back to the top

STEPS TO REPRODUCE
====================

1. Using Visual Studio 2005 or Visual Studio 2008, create a new C# Windows Forms application.
2. Add a TreeView control to the form named treeView1.
3. Set the TreeView control’s ShowNodeToolTips property to True.
4. Add a ToolTip control to the form named toolTip1.
5. Add the following code to the form’s Load event handler:

  private void Form1_Load(object sender, EventArgs e)
        {
            for (int i = 0; i < 10; i++)
            {
                TreeNode newNode = new TreeNode();
                newNode.Text = test node + i.ToString();
                newNode.Tag = i.ToString();
                treeView1.Nodes.Add(newNode);
            }
        }

6. Add the following code to the MouseMove event handler of the TreeView control:

  private void treeView1_MouseMove(object sender, MouseEventArgs e)
        {
            TreeView tv = sender as TreeView;
            if (tv != null)
            {
                TreeNode tn = tv.GetNodeAt(new Point(e.X, e.Y));
                if (tn != null)
                {
                    this.toolTip1.SetToolTip(tv, tn.Text);
                }
            }
        }

7. Build the application and run it.
8. Hover the mouse over several nodes in the TreeView control.
9. Close the form to exit the application.

You should receive one of the errors listed in the Result section above.

When running the application under a native code debugger, you may also see an Access Violation occurring in the following call stack.

mscorlib_ni!System.Runtime.InteropServices.Marshal.PtrToStructure(IntPtr, System.Type)+0×5d
System.Windows.Forms.UnsafeNativeMethods.PtrToStructure(IntPtr, System.Type)+0×25
System_Windows_Forms_ni!System.Windows.Forms.TreeView.WmNeedText(System.Windows.Forms.Message ByRef)+0×35
System_Windows_Forms_ni!System.Windows.Forms.TreeView.WndProc(System.Windows.Forms.Message ByRef)+0×36e281
System_Windows_Forms_ni!System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)+0xd
System_Windows_Forms_ni!System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)+0×36
System_Windows_Forms_ni!System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)+0×5a
user32!InternalCallWinProc+0×23
user32!UserCallWinProcCheckWow+0×14b
user32!CallWindowProcAorW+0×97
user32!CallWindowProcW+0×1b
comctl32!CallOriginalWndProc+0×1a
comctl32!CallNextSubclassProc+0×3c
comctl32!DefSubclassProc+0×46
comctl32!TTSubclassProc+0×59
comctl32!CallNextSubclassProc+0×3c

Back to the top

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top

Back to the top

Additionally, the taskbar does not appear. You have limited access to Windows Vista programs and to Windows Vista features.

Back to the top

Notes

•	To use the Automated phone system activation option, click Show me other ways to activate.
•	For more information about the Windows Vista activation process, click Read our privacy statement.

Back to the top

For more information about reduced-functionality mode, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

This article contains download and support information, installation notes, and general usage information about Network Monitor 3. Network Monitor 3.1 is the latest version.

Back to the top

Download and support information

To download Network Monitor 3.1 visit the following Microsoft Web sites:

Support information for Network Monitor 3 is located at the following Microsoft Connect Web site:

You must sign in to the Web site by using a Windows Live ID. After you sign in, you can apply to participate in the program. To do this, in the Options column of the table, click Apply next to Network Monitor 3. After you enroll in the program, you have access to newsgroups, and you can submit bug reports.

Installation notes

Network Monitor 3.1 can co-exist with earlier versions of Network Monitor. By default, Network Monitor 3.1 is installed in the %Program Files% Microsoft Network Monitor 3.0 folder. Therefore, conflicts do not occur if an earlier version is installed in a different folder on the computer. When you install Network Monitor 3.1, Network Monitor 3 is uninstalled.

Network Monitor 3.1 includes a new driver for Windows Vista-based computers. This new driver supports new features of the Network Driver Interface Specification (NDIS) 6.0 driver. If you are using tools that rely on Network Monitor 2.x NPPTools, the tools will no longer work. To capture network data in Windows Vista, you must use Network Monitor 3.1. Network Monitor 2.x does not capture network data correctly in Windows Vista.

Suggested hardware to run Network Monitor 3.1 is listed as follows:

•	1 GHz or faster processor
•	1 GB or more memory
•	25 MB free space on the hard disk, and additional hard disk space to store capture files

Network Monitor 3.1 is supported on the following operating systems:

•	Windows Vista
•	Microsoft Windows XP
•	Microsoft Windows Server 2003

Warnings and cautions

Currently, we do not recommend that you run Network Monitor 3 on production systems. In scenarios where load is something to consider, use the command-line version of Network Monitor 3 to capture network data. The command-line version is Nmcap.exe. For more information about Nmcap.exe, see the Nmcap.exe command-line tool section.

Network Monitor 3 may consume lots of system resources. Some things to consider are listed as follows.

•	Disk space When you start a capture session, Network Monitor 3 stores frames in a sequence of capture files that are located in the Temp folder. By default, the size of each capture file is 20 MB. By default, if you do not stop the capture session, Network Monitor 3 continues to store capture files in the Temp folder until the free hard disk space on the computer is less than 2 percent. Then, Network Monitor 3 stops the capture session. You can configure the capture file size, the location where the capture files are stored, the free hard disk space limit, and other capture options. To do this, on the Tools menu, point to Options, and then click the Capture tab.
•	Memory use In addition to capturing data, Network Monitor 3 assigns properties to frames, and then uses the properties to group the frames into conversations. Network Monitor 3 displays the conversations and the associated frames in a tree structure in the Network Conversations pane. The Conversations feature of Network Monitor 3 significantly increases memory use. This may cause the computer to become unresponsive. By default, the Conversations feature is turned off. Some higher-level protocol filters require conversation properties. To turn on the Conversations feature, click the Start Page tab, and then click to select the Enable Conversations check box.
•	Processor utilization The Conversations feature of Network Monitor 3 may significantly increase processor utilization when lots of frames are processed. By default, the Conversations feature is turned off, as mentioned in the Memory use section.

General usage

General usage information for Network Monitor 3 is listed as follows.

•	Capture network data As mentioned earlier, Network Monitor 3 may consume lots of system resources. Therefore, if you want to minimize the effect on system resources that may occur when you use Network Monitor 3 to capture data, use the Nmcap.exe command-line tool to capture data. Network Monitor 3 enables you to collect network data and to view the network data in real time as the data is captured. To start a capture session in Network Monitor 3, click the Start Page tab, click Create a new capture tab, and then either click the Start Capture button, or press F10.
•	Filters Network Monitor 3 uses a simple syntax that is expression-based to filter frames. All frames that match the expression are displayed to the user. For more information about filters, do any of the following: • View the topics in the Using Filters section of the Network Monitor 3 User’s Guide. To do this, on the Help menu, click Contents, and then double-click Using Filters. • On the Help menu, point to How Do I , and then click Use Filters. • Use the Capture Filter tab or the Display Filter tab to view standard filters.
•	Conversations By default, the Conversations feature is turned off. This is the default setting because the Conversations feature can consume lots of memory, especially in scenarios when you capture data for long periods of time. To turn on the Conversations feature, click the Start Page tab, and then click to select the Enable Conversations check box. When you turn on the Conversations feature, frames are grouped and displayed in the Network Conversations pane in a tree structure according to the conversations to which they belong. For example, TCP data that uses the same source port and the same destination port is organized into a group. When you click a node in the Network Conversations pane, the corresponding conversation filter is automatically applied to the frames in the Frame Summary pane. Only frames that belong to that particular conversation are displayed.
•	Nmcap.exe command-line tool The Nmcap.exe command-line tool enables you to configure when you want to start a capture session or to stop a capture session. You can also use the Nmcap.exe command-line tool to created chained captures. Chained captures enable you to create multiple capture files. However, the size of the capture files remains small.
•	Network Parsing Language (NPL) Network Monitor 3 parsers are written in a language specifically to make parser development more straightforward. This also provides a level of protection against potential exploitation from malicious code that may occur if parsers were created as DLL files. NPL provides access to parsers. You can view or modify the parsers that are included in Network Monitor 3.

Common issues

Common issues include the following:

•

Protocols may not parse correctly. This issue may occur if either of the following conditions is true: • The Conversations feature is turned off. Certain protocols depend on conversation properties to store state values that may be needed in later frames. For example, TCP needs conversations to store information about retransmitted frames. The filter for TCP Retransmits will not work unless the Conversations feature is enabled. Similarly, the Server Message Block (SMB) protocol cannot translate the response to a Transact command, because the response does not contain the original command. The information is saved in conversation properties. • The parser and the associated protocol may be available under the Microsoft Communications Protocol Program (MCPP) and the Microsoft Work Group Server Protocol Program (WSPP). To learn more about how to become a licensee, visit the following Microsoft Web site: http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx (http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx) These parsers are considered confidential Microsoft intellectual property and are not distributed publicly. Therefore, these parsers are not part of the publicly-released version of Network Monitor 3

•

You receive one of the following error messages when you run Network Monitor 3 on a Windows Vista-based computer: None of the network adapters are bound to the Netmon driver This network adapter is not configured to capture with Network Monitor This issue occurs if either of the following conditions is true: • You are not running Network Monitor 3 as administrator. • You are not a member of the Netmon Users group. For more information, see the Network Monitor 3 releases notes or see the Operating on Windows Vista topic in Network Monitor 3 Help.

Back to the top

Back to the top

You cannot print the files that are stored on the memory card.

When this problem occurs, you may be able to use Windows Photo Gallery or Windows Live Photo Gallery to open the files on the memory card. However, you cannot save a file to the memory card by using a different name.

The memory card reader may support any of the following memory cards in addition to other memory cards:

•	CompactFlash Type I
•	CompactFlash Type II
•	IBM Microdrive
•	Memory Stick
•	Secure Digital MultiMediaCard (MMC)
•	xD Picture Card

Back to the top

Windows Vista

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista, 32-bit (x86-based) versions

File name	File version	File size	Date	Time	Platform
Kernel32.dll	6.0.6000.20530	875,008	06-Feb-2007	03:39	x86
Update.mum	Not Applicable	2,658	06-Feb-2007	21:26	Not Applicable
X86_8d6afd7e8f012a1b02284591048198e4_31bf3856ad364e35_6.0.6000.20530_none_060d2bc2b80a3c59.manifest	Not Applicable	696	06-Feb-2007	21:26	Not Applicable
X86_a65933bf6493d2b289a8b58095cfc797_31bf3856ad364e35_6.0.6000.20530_none_a392d5094e963b68.manifest	Not Applicable	695	06-Feb-2007	21:26	Not Applicable
X86_microsoft-windows-kernel32_31bf3856ad364e35_6.0.6000.20530_none_9240cfd6725af10c.manifest	Not Applicable	4,839	06-Feb-2007	21:30	Not Applicable
X86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20530_none_6aac15732e0b561d.manifest	Not Applicable	975,772	06-Feb-2007	21:30	Not Applicable
Shell32-ppdlic.xrm-ms	Not Applicable	3,150	06-Feb-2007	03:22	Not Applicable
Shell32.dll	6.0.6000.20530	11,314,688	06-Feb-2007	03:40	x86

Windows Vista, 64-bit versions

File name	File version	File size	Date	Time	Platform
Kernel32.dll	6.0.6000.20530	875,008	06-Feb-2007	03:39	x86
Update.mum	Not Applicable	2,658	06-Feb-2007	21:26	Not Applicable
X86_8d6afd7e8f012a1b02284591048198e4_31bf3856ad364e35_6.0.6000.20530_none_060d2bc2b80a3c59.manifest	Not Applicable	696	06-Feb-2007	21:26	Not Applicable
X86_a65933bf6493d2b289a8b58095cfc797_31bf3856ad364e35_6.0.6000.20530_none_a392d5094e963b68.manifest	Not Applicable	695	06-Feb-2007	21:26	Not Applicable
X86_microsoft-windows-kernel32_31bf3856ad364e35_6.0.6000.20530_none_9240cfd6725af10c.manifest	Not Applicable	4,839	06-Feb-2007	21:30	Not Applicable
X86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20530_none_6aac15732e0b561d.manifest	Not Applicable	975,772	06-Feb-2007	21:30	Not Applicable
Shell32-ppdlic.xrm-ms	Not Applicable	3,150	06-Feb-2007	03:22	Not Applicable
Shell32.dll	6.0.6000.20530	11,314,688	06-Feb-2007	03:40	x86

Back to the top

Back to the top

For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

Update information

The following files are available for download from the MicrosoftDownload Center:

Windows Vista, 32-bit versions
Download the Windows6.0-KB930955-x86.msu package now. (http://www.microsoft.com/downloads/details.aspx?familyid=9106B9D4-BAA8-4C29-A605-A4D09C04A5F3)

Windows Vista, 64-bit versions
Download the Windows6.0-KB930955-x64.msu package now. (http://www.microsoft.com/downloads/details.aspx?familyid=D812B06B-0601-4755-98D3-878093CAD40C)For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Prerequisites

To apply this update, you must have Windows Vista installed.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, 32-bit versions

Windows Vista, 64-bit versions

Back to the top

Information about how to use the User Profile WMI provider

Visual Basic script examples

strComputer =. Set objAccount = GetObject(winmgmts:{impersonationLevel=impersonate}!   _                            & strComputer & root cimv2:Win32_UserAccount. _                            &Domain='contoso',Name='fabrikam')     Set objUserProfile = GetObject(winmgmts:{impersonationlevel=impersonate}!   _                               & strComputer & root cimv2:Win32_UserProfile. _                               &SID=' & objAccount.SID &') objUserProfile.Delete_

strComputer =.Set objWMIService = GetObject(winmgmts:   & strComputer & root cimv2)Set colProfiles = objWMIService.ExecQuery(Select * from Win32_UserProfile)For Each objProfile in colProfiles    Set objSID = objWMIService.Get(Win32_SID.SID=' & objProfile.SID &')    Wscript.Echo======================================================& VBNewLine _        &Sid: & objProfile.Sid & VBNewLine _        &User Name: & objSID.AccountName & VBNewLine _        &User Domain: & objSID.ReferencedDomainName & VBNewLine _        &LocalPath: & objProfile.LocalPath & VBNewLine _        &Loaded: & objProfile.Loaded & VBNewLine _        &RefCount: & objProfile.RefCount & VBNewLine _        &RoamingConfigured: & objProfile.RoamingConfigured & VBNewLine _        &RoamingPath: & objProfile.RoamingPath & VBNewLine  _        &RoamingPreference: & objProfile.RoamingPreference & VBNewLine _        &Status: & objProfile.Status & VBNewLine _        &LastUseTime: & objProfile.LastUseTime & VBNewLine  _        &LastDownloadTime: & objProfile.LastDownloadTime & VBNewLine  _        &LastUploadTime: & objProfile.LastUploadTime & VBNewLine  Next

Back to the top

Back to the top

Back to the top

Back to the top

Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2008 Service Pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix, you must have Windows Server 2008 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, IA-64 version

Back to the top

Back to the top

Back to the top

How to obtain help and support for this security update

For home users, support is available at no charge by calling 1-866-PCSAFETY in the United States and in Canada or by contacting your local Microsoft subsidiary. For more information about how to contact your local Microsoft subsidiary for security update support issues, visit the following International Support Web site:

For enterprise customers, support for security updates is available through your usual support contacts.

Back to the top

Removal information

To remove this security update, use the Add or Remove Programs feature in Control Panel.

Back to the top

However, when a fatal system error occurs, and you receive a Stop error message, no dump file is generated. Or, an invalid dump file is generated.

Back to the top

Back to the top

Windows Vista hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available section and the online request forms display the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

Windows Vista with Service Pack 1, x86-based versions

Back to the top

Windows Server 2008 hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a Hotfix download available section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Note The Hotfix download available section and the online request forms display the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2008, x86-based versions

Back to the top

Back to the top

Back to the top

This issue occurs if the following conditions are true:

• There is a bitmap on the same page as the equation.
• The 2007 Microsoft Office system is installed on a Windows XP-based or Windows Server 2003-based computer.
• The Complex Script support files are not installed.

1. Click Start, and then click Run
2. Type intl.cpl, and then click OK.
3. Click the Languages tab.
4. Under Supplemental language support, click to select the Install files for complex script and right-to-left languages (including Thai) check box.
5. When you receive the following message, click OK to close the message:
   You chose to install the Arabic, Armenian, Georgian, Hebrew, Indic, Thai and Vietnamese language files. This will require 10 MB or more of available disk space. The files will be installed after you click OK or Apply on the Regional and Language Options dialog box.
6. Click OK to close the Regional and Language Options dialog box.

Although the ImageX.exe tool may appear to be a mechanism to create an image of a computer for backup, there are several issues that prevent using the ImageX.exe tool as a supported backup mechanism.

The following are the issues when you use the ImageX.exe tool as a backup mechanism:

•	Extended attributes are lost.
•	The ImageX.exe tool only applies reparse points that are symbolic links or junctions.
•	Sparse files on the system are captured and applied. However, the sparse files are no longer sparse after they have been applied.
•	Object IDs on files are lost in the capture process or in the apply process.

Note The $WINDOWS.OLD folder is a hidden system folder. Sometimes, this folder has a name other than $WINDOWS.OLD. For example, this folder may be named $WINDOWS.~Q. For information about how to view this folder, see the More Information section.

Back to the top

Back to the top

Important Make sure that you back up any important data that is located in the $WINDOWS.OLD folder before you follow these steps.

Back to the top

Method 1: Use the Disk Cleanup tool

The Disk Cleanup tool (Cleanmgr.exe) is included with Windows Vista. You can use this tool to remove the $WINDOWS.OLD folder together with its contents. To do this, follow these steps:

1.	Click Start, and then click Computer.
2.	Right-click the hard disk from which you want to remove the $WINDOWS.OLD folder, and then click Properties.
3.	Click the General tab, and then click Disk Cleanup.
4.	Click Files from all users on this computer. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
5.	In the File to delete list, click to select the File discarded by Windows upgrade check box. Note Click to clear other check boxes, depending on the other files that you want to remove.
6.	Click OK, and then click Delete Files to confirm that you want to permanently remove the $WINDOWS.OLD folder together with its subfolders and files.

Back to the top

Method 2: Use the RD command

You can use the RD (Remove Directory) command-line command to remove the $WINDOWS.OLD folder together with its contents. To do this, follow these steps:

1.	Click Start, type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
2.	Type cd , and then press ENTER to change to the root directory of the current drive. Generally, this is drive C.
3.	Type drive:, and then press ENTER to change to the drive from which you want to remove the $WINDOWS.OLD folder. For example, if the $WINDOWS.OLD folder is on drive D, type d:, and then press ENTER. Note If the command prompt is already at the correct drive, skip this step.
4.	Type rd $windows.old /s, and then press ENTER to remove the $WINDOWS.OLD folder together with its subfolders.
5.	When you are prompted to confirm the removal of the $WINDOWS.OLD folder, type y, and then press ENTER.

For more information about how to use the RD command, type rd /? at a command prompt, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Back to the top

Back to the top

How to view the $WINDOWS.OLD folder

1.	Click Start, type folder options in the Start Search box, and then click Folder Options in the Programs list. If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
2.	Click the View tab, click Show hidden files and folders, and then click to clear the following two check boxes: Hide extensions for known file types Hide protected operating system files (Recommended)
3.	Click Yes to confirm that you want to display operating system files, and then click OK.

Back to the top