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. You may see the following symptoms.
Back to the top

Symptom 1: Windows PowerShell 1.0 fails when a custom locale is set
If 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.

When you click Close Program, Windows PowerShell 1.0 crashes, and an event that resembles the following is recorded in the Application log:

Log Name: Application
Source: .NET Runtime
Date: Date
Event ID: 1023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: ComputerName
Description: .NET Runtime version 2.0.50727.312 - Culture ID 3072 (0x0C00) is not a supported culture. Parameter name: culture

Symptom 2: Cannot access the root of the file system drive
If 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.