Article ID: 941660 - Last Review: May 20, 2008 - Revision: 2.2 Windows PowerShell 1.0 does not work correctly with custom locales or with programs that prevent Windows PowerShell 1.0 from accessing the root of each file system drive in Windows Vista, in Windows Server 2003, and in Windows XP
On This PageSYMPTOMSWindows PowerShell 1.0 does not work correctly with custom locales or with programs that prevent Windows PowerShell 1.0 from accessing the root of each file system drive. You may see the following symptoms. Symptom 1: Windows PowerShell 1.0 fails when a custom locale is setIf the operating system uses a custom locale (The custom locale is set in the Regional and Language Options item in Control Panel.), Windows PowerShell 1.0 fails when you try to start Windows PowerShell. When Windows PowerShell 1.0 fails, it displays an error message that resembles the following:PowerShell.EXE has stopped working A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
Symptom 2: Cannot access the root of the file system driveIf Windows PowerShell 1.0 cannot access the root of a file system drive, Windows PowerShell displays an error message that reports an unhandled exception.For example, after you install Microsoft SoftGrid on the computer, Windows PowerShell 1.0 throws an exception when the computer starts. If you use the Get-PsDrive cmdlet to list the available drives, the drive on which SoftGrid is installed together with any remaining drives do not appear in the resulting drive list. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:935791
(http://support.microsoft.com/kb/935791/
)
How to obtain the latest Windows Vista service pack Hotfix informationWindows VistaA 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.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 Customer Service and Support to obtain the hotfix. 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays 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.PrerequisitesTo apply this hotfix, Windows PowerShell 1.0 must be installed on the computer.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationThis hotfix requires no changes to the registry.File informationThe 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 versions Collapse this table
Collapse this table
Windows XPA 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.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 Customer Service and Support to obtain the hotfix. 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays 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.PrerequisitesTo apply this hotfix, Windows PowerShell 1.0 together with Windows XP Service Pack 2 must be installed on the computer.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationThis hotfix requires no changes to the registry.File informationThe 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 XP, x86-based versions Collapse this table
Windows Server 2003A 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.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 Customer Service and Support to obtain the hotfix. 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays 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.PrerequisitesTo apply this hotfix, Windows PowerShell 1.0 must be installed on the computer. Additionally, one of the following service packs must be installed on the computer:
Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other previously released hotfixes.Registry informationThis hotfix requires no changes to the registry.File informationThe 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 2003, x86-based versions Collapse this table
Collapse this table
Collapse this table
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1. MORE INFORMATIONWindows PowerShell is a new command line shell and scripting language that can be used for system administration. Windows PowerShell can also be used to manage applications that run on Windows. Windows PowerShell helps speed up automation, and Windows PowerShell is easy for organizations to learn and to use so that they can achieve better productivity and better control. For more information about Windows PowerShell 1.0, click the following article numbers to view the articles in the Microsoft Knowledge Base: 928439
(http://support.microsoft.com/kb/928439/
)
Windows PowerShell 1.0 Installation Package for Windows Vista
926139
(http://support.microsoft.com/kb/926139/
)
Windows PowerShell 1.0 English Language Installation Packages for Windows Server 2003 and for Windows XP
926140
(http://support.microsoft.com/kb/926140/
)
Windows PowerShell 1.0 Localized Installation Package for Windows Server 2003 and for Windows XP
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:824684
(http://support.microsoft.com/kb/824684/LN/
)
Description of the standard terminology that is used to describe Microsoft software updates APPLIES TO
| Article Translations
|
Back to the top
