Fix Policy.1.0.Microsoft.Powershell.Commands.Utility.config Errors

Sometimes Windows system displays error messages regarding corrupted or missing Policy.1.0.Microsoft.Powershell.Commands.Utility.config files. Situations like that can occur, for example, during a software installation process. Each software program requires certain resources, libraries, and source data to work properly. Corrupted or nonexistent Policy.1.0.Microsoft.Powershell.Commands.Utility.config file can therefore effect in failed execution of the started process.

Policy.1.0.Microsoft.Powershell.Commands.Utility.config file Configuration. The file was developed by Microsoft for use with Windows software. Here you will find detailed information about the file and instructions how to proceed in the event of Policy.1.0.Microsoft.Powershell.Commands.Utility.config related errors on your device. You can also download Policy.1.0.Microsoft.Powershell.Commands.Utility.config file compatible with Windows 10, Windows 8.1, Windows 8 devices which will (most probably) allow you to solve the problem.

For Windows Compatible with: Windows 10, Windows 8.1, Windows 8

File info

General information
Filename Policy.1.0.Microsoft.Powershell.Commands.Utility.config
File extension CONFIG
Type Developer
Description Configuration
Program Windows 10
Software Windows
Author Microsoft
Software version 10
File size 936
Oldest file 2012-06-02
Latest file 2017-03-18
Fix File Errors

There are various types of errors related to Policy.1.0.Microsoft.Powershell.Commands.Utility.config file. Policy.1.0.Microsoft.Powershell.Commands.Utility.config file may be located in wrong file directory on your device, may not be present in the system, or may be infected with malicious software and therefore not work correctly. Below is a list of most common error messages related to Policy.1.0.Microsoft.Powershell.Commands.Utility.config file. If you encounter one listed below (or similar), please consider the following suggestions.

  • Policy.1.0.Microsoft.Powershell.Commands.Utility.config is corrupted
  • Policy.1.0.Microsoft.Powershell.Commands.Utility.config cannot be located
  • Runtime Error - Policy.1.0.Microsoft.Powershell.Commands.Utility.config
  • Policy.1.0.Microsoft.Powershell.Commands.Utility.config file error
  • Policy.1.0.Microsoft.Powershell.Commands.Utility.config file cannot be loaded. Module was not found
  • cannot register Policy.1.0.Microsoft.Powershell.Commands.Utility.config file:
  • Policy.1.0.Microsoft.Powershell.Commands.Utility.config file could not be loaded
  • Policy.1.0.Microsoft.Powershell.Commands.Utility.config file doesn't exist



Application could not be started because Policy.1.0.Microsoft.Powershell.Commands.Utility.config file is missing. Reinstall the application to solve the problem.


Problems related to Policy.1.0.Microsoft.Powershell.Commands.Utility.config can be addressed in various ways. Some methods are meant only for advanced users. If you don't have confidence in your skills, we suggest consulting a specialist. Fixing Policy.1.0.Microsoft.Powershell.Commands.Utility.config file errors should be approached with utmost caution for any mistakes can result in unstable or unproperly working system. If you have the necassary skills, please proceed.

Policy.1.0.Microsoft.Powershell.Commands.Utility.config file errors can be caused by various factors, so its is beneficial to try to fix them using various methods.

Step 1: Scan your computer for any malicious software

Virus Scan

Windows files are commonly attacked by malicious software that prevents them from working properly. First step in addressing problems with Policy.1.0.Microsoft.Powershell.Commands.Utility.config file or any other Windows system files should be scanning the system for malicious software using an antivirus tool.

If by any chance you don't have any antivirus software installed on your system yet, you should do it immediately. Unprotected system is not only a source of file errors, but, more importantly, makes your system vulnerable to many dangers. If you don't know which antivirus tool to choose, consult this Wikipedia article – comparison of antivirus software.

Step 2: Update your system and drivers.

Windows Update

Installing relevant Microsoft Windows patches and updates may solve your problems related to Policy.1.0.Microsoft.Powershell.Commands.Utility.config file. Use dedicated Windows tool to perform the update.

  1. Go to the Windows "Start" menu
  2. Type "Windows Update" in the search field
  3. Choose the appropriate software program (name may vary depending on your system version)
  4. Check if your system is up to date. If any unapplied updates are listed, install them immediately.
  5. After the update has been done,restart your computer in order to complete the process.

Beside updating the system, it is recommended that you install latest device drivers, as drivers can influence proper working of Policy.1.0.Microsoft.Powershell.Commands.Utility.config or other system files. In order to do so, go to your computer or device producer's website where you will find information regarding latest driver updates.

Step 3: Use System File Checker (SFC) tool

System File Checker

System File Checker is a Microsoft Windows tool. As the name suggests, the tool is used for identyfing and addressing system file related errors, including those related to Policy.1.0.Microsoft.Powershell.Commands.Utility.config file. After an error related to%fileextension% file has been discovered, the program attempts to automatically replace the Policy.1.0.Microsoft.Powershell.Commands.Utility.config file with properly working version. To use the tool:

  1. Go to the Windows "Start" menu
  2. Type "cmd" in the search field
  3. Locate "Command Prompt" result – don't run it yet:
  4. Click the right mouse button and select "Run as Administrator" option
  5. Type "sfc /scannow" in console prompt to start the program and follow the instructions

Step 4: Restoring Windows system

Windows Recovery

Another approach is to restore system to previous state, before the Policy.1.0.Microsoft.Powershell.Commands.Utility.config file error occured. In order to restore your system, follow the instructions below

  1. Go to the Windows "Start" menu
  2. Type "System Restore" in the search field
  3. Start the system restore tool – it's name may differ depending on version of the system
  4. The application will guide you through the process – read the messages carefully
  5. After the process has finished, restart your computer.

If all the above-mentioned methods failed and the Policy.1.0.Microsoft.Powershell.Commands.Utility.config file problem has not been resolved, proceed to the next step. Remember that the following steps are intended only for advanced users.

Download and replace Policy.1.0.Microsoft.Powershell.Commands.Utility.config file

The last solution is to manually download and replace Policy.1.0.Microsoft.Powershell.Commands.Utility.config file in appropriate folder on the disk. Select file version compatible with your operating system and click the "Download" button. Next, go to your web browser's "Downloaded" folder and copy the downloaded Policy.1.0.Microsoft.Powershell.Commands.Utility.config file.

Go to the folder where the file should be located and paste the downloaded file. Below is the list of Policy.1.0.Microsoft.Powershell.Commands.Utility.config file example directory paths.

  • Windows 10: C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Policy.1.0.Microsoft.PowerShell.Commands.Utility\v4.0_1.0.0.0__31bf3856ad364e35\
  • Windows 8.1: ---
  • Windows 8: ---

If the steps did not solve your Policy.1.0.Microsoft.Powershell.Commands.Utility.config file problem, you should consult a professional. A probability exists that the error(s) might be device-related and therefore should be resolved at the hardware level. A fresh operating system installation might be necessary – a faulty system installation process can result in data loss.

File versions list

Filename Policy.1.0.Microsoft.Powershell.Commands.Utility.config
System Windows 10
File size 936 bytes
Date -0001-11-30
File details
MD5 b90a26d41f79e7533d7c388fcf224ead
SHA1 7e0e72a1c5724133391dd8c18e10081649a69380
SHA256 e5211646208b5c3fd17de0e6683ce29d9b3e905e2f878d1ef466d2a5ce8be45e
CRC32 d63582bc
Example file location C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Policy.1.0.Microsoft.PowerShell.Commands.Utility\v4.0_1.0.0.0__31bf3856ad364e35\
Filename Policy.1.0.Microsoft.Powershell.Commands.Utility.config
System Windows 8.1
File size 936 bytes
Date -0001-11-30
File details
MD5 b90a26d41f79e7533d7c388fcf224ead
SHA1 7e0e72a1c5724133391dd8c18e10081649a69380
SHA256 e5211646208b5c3fd17de0e6683ce29d9b3e905e2f878d1ef466d2a5ce8be45e
CRC32 d63582bc
Example file location ---
Filename Policy.1.0.Microsoft.Powershell.Commands.Utility.config
System Windows 8
File size 936 bytes
Date -0001-11-30
File details
MD5 b90a26d41f79e7533d7c388fcf224ead
SHA1 7e0e72a1c5724133391dd8c18e10081649a69380
SHA256 e5211646208b5c3fd17de0e6683ce29d9b3e905e2f878d1ef466d2a5ce8be45e
CRC32 d63582bc
Example file location ---