Load module error 0x800

load module error 0x800

Windows update has an error code_ 800700C1 · Solve the problem that comdlg32.ocx, mscomm32.ocx and other controls cannot be registered under. This can occur when the PowerShell script execution policy has not been set to RemoteSigned. Resolution. Manually follow the instructions in. This is a window error code problem. This error usually occurs during the installation or the windows update process or by specific applications. The error may.

Load module error 0x800 - are

Problem: When trying to import the PnP PowerShell module, I got an error message “Import-Module: The specified module ‘SharePointPnPPowerShellOnline’ was not loaded because no valid module file was found in any module directory”.

You may face this trouble for other PowerShell modules as well. E.g.

  • “import-module : the specified module ‘activedirectory’ was not loaded because no valid module file was found in any module directory.”
  • “import-module : the specified module ‘exchangeonlinemanagement’ was not loaded because no valid module file was found in any module directory.”
  • “import-module : the specified module ‘sqlserver’ was not loaded because no valid module file was found in any module directory.”
Import-Module: The specified module was not loaded because no valid module file was found in any module directory

Solution:

This error is because the PowerShell console or ISE is unable to get the module from given module path’s in the environment variable “PSModulePath”. To fix the issue, You have to make sure your custom module’s path is appended to the PSModulePath environment variable.

Step 1: Get the Path of your custom PowerShell Module.

Make sure you have the custom module installed already. To get the modules installed, Open PowerShell console and type:

Get-module -ListAvailable

This gets all installed modules in your system along with their installed Path. Get the path of your custom module as highlighted. In my case, the PnP PowerShell module was installed at “C:\Program Files\WindowsPowerShell\Modules”.

Get-module -ListAvailable

Step 2: Verify if the custom module’s path is added to the “PSModulePath”

As the next step, we have to verify if our custom module’s path is added to the “PSModulePath” variable.

  • Go to System Properties by pressing Windows Key + Pause Break (Or Go to File Explorer >> Right click on “This PC” >> Properties) >> Click on Advanced System Settings >> Click on Environment Variables
  • Pick “PSModulePath” and click on “Edit” button.
    add path to PSModulePath variable
  • Append your PowerShell Module path to this variable. In my case, its “C:\Program Files\WindowsPowerShell\Modules”, separated by ; (semicolon). From Windows 10 onwards, we have a neat option to add new path. Hit “New” button and add the module’s path there.add to psmodulepath
  • Restart PowerShell ISE or PowerShell console.

This should solve the problem.

Related Posts

aford10 :

That looks like it has something to do with mobile device software. Did you install any software for a mobile device? If so, and it's not important, just uninstall it.

If it is important, browse to that folder location and see if the .dll is there. If it is, just re-register the .dll. If the .dll is there, and you want to register it, I can tell you how, but I'd need the whole file path.



No nothing of the sort. This error popped up after MalwareBytes restarted my computer after completing a scan

I went to "C:\Users\Andrew\AppData\Local" to look for the folder but it is not there (search didnt find it either)

in the registry it's no longer there but the popups persist.




I checked msconfig for anything that shouldnt be starting up I will do a clean boot to see if that corrects the problem.



edit: The errors didnt come up when I did a diagnostic startup. on normal startup they do.

Im not sure how to get the whole file path since it doesn't exist

The .DLL is most definitely not important.



When I do a selective startup and dont load any startup programs the errors dont popup

I already combed through msconfig to see if theres anything that shouldnt be there

Would the problem be in services.msi causing whatever that is to startup?

 

500.50 error using URL Rewrite

I ran into a 500.50 error yesterday, which wasn’t very descriptive initially, so I thought I would provide some details on what it could be.

First, off, if you hit the page remotely, it’s going to hide the real details.  It will look something like this:

Server Error

500 - Internal server error.

There is a problem with the resource you are looking for, and it cannot be displayed.

Checking the IIS logs will show that it’s a 500.50 error in this case.

The first thing to do after running into a general error like this is to test it locally on the server.  Now you get a lot more information (I’ve included just some of the error details below):

HTTP Error 500.50 - URL Rewrite Module Error.

The server variable "HTTP_HOST" is not allowed to be set. Add the server variable name to the allowed server variable list.

Now we can tell exactly what happened.  I’m using URL Rewrite 2.0.  Version 2 now allows updating Server Variables.  I tried to update the HTTP_HOST server variable at the site level but forgot to add HTTP_HOST as an approved server variable.

To fix this issue, go to View Server Variables in the Actions pane of URL Rewrite.  Note that you will only see these if you are an administrator on the server.

image

Now add the server variable that you want to change at the site level:

image

That resolved my situation.  However, a 500.50 error can be used for a number of things, always URL Rewrite related. 

Here’s the official description of a 500.50 error:

500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.

500.51, 500.52 and 500.53 are also URL Rewrite Related: http://support.microsoft.com/kb/943891

Here are a couple other posts of 500.50 situations:

http://forums.iis.net/t/1164360.aspx
http://www.digitalpimple.com/tutorials/windows-tutorials/fix-550-rewrite-error/ (I believe the author meant 500.50)

Hope that helps someone, and happy URL Rewriting!

This usually happens when the OSCE/Apex One server is installed in the same box as Windows Server Update Services (WSUS).

Error Code 0x8007007e is:

ERROR_MOD_NOT_FOUND – The specified module could not be found.

  • From IIS log, the error is "500 19 126". sc-win32-status is 126. #Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken 2021-04-29 14:53:18 10.80.44.81 GET /officescan/default.htm - 4343 - 10.80.44.81 Mozilla/4.0+ (compatible;+MSIE+7.0;+Windows+NT+10.0;+WOW64;+Trident/7.0;+.NET4.0C;+.NET4.0E;+.NET+CLR+2.0.50727; +.NET+CLR+3.0.30729;+.NET+CLR+3.5.30729) - 500 19 126 773
  • 126 means ERROR_MOD_NOT_FOUND means the specified module could not be found. You may refer to this Microsoft article for the list of error codes: .

    The following is also found in the ApplicationHost.config, which shows the possibility that it was modified by the user:

    Line 170-176: <key path="LM/W3SVC/FILTERS/COMPRESSION/xpress"> <property id="2243" dataType="DWord" userType="1" attributes="None" value="0" /> <property id="2215" dataType="DWord" userType="1" attributes="None" value="0" /> <property id="2238" dataType="MultiSZ" userType="1" attributes="None" value="" /> <property id="2240" dataType="DWord" userType="1" attributes="None" value="1" /> <property id="2244" dataType="MultiSZ" userType="1" attributes="None" value="asmx " /> </key> Line 358: <scheme name="xpress" doStaticCompression="false" doDynamicCompression="true" dll="C:\Program Files\Update Services\WebServices\suscomp.dll" staticCompressionLevel="10" dynamicCompressionLevel="0" />

This problem occurs because the ApplicationHost.config file or the Web.config file references a module that is invalid or that does not exist.

Based on the Detailed Error Information, the DynamicCompressionModule module is causing the trouble. This is because of the XPress compression scheme module (suscomp.dll) that gets installed with WSUS. Since compression schemes are defined globally and try to load in every application Pool, it will result in this error when a 64-bit version of suscomp.dll attempts to load in an application pool running in 32-bit mode.

This module entry looks like:

<scheme name="xpress" doStaticCompression="false" doDynamicCompression="true" dll="C:\Windows\system32\inetsrv\suscomp.dll" staticCompressionLevel="10" dynamicCompressionLevel="0" />

Do one of the following to resolve the issue:

  • Remove/Disable the XPress compression scheme from the configuration:
    1. Open Command Prompt.
    2. Navigate to "%windir%\system32\inetsrv".
    3. Run the following command:
      "appcmd.exe set config -section:system.webServer/httpCompression /-[name=’xpress’]"
  • Use a 32-bit version of suscomp.dll.
  • Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools

If you are getting frustrated from Windows Error 0x80070005 Code PC problem on your computer, then read and check out this below post once to find that how we quickly fix and solve this type of issue from your Windows PC. Today we are here going to show you how to fix this simple error code problem.

This shows an error code message like,

Error 0x80070005

The call loaded the module “.dll” to DllRegisterServer failed with Error Code 0x80070005 Xbox.

For more information about this problem, search online using the Windows Update Error 0x80070005 as a search term.

This is a window error code problem. This error usually occurs during the installation or the windows update process or by specific applications. The error may also happen if you don’t have an administrator’s permission & there are many user accounts to access the PC. It usually occurs when you lack file or registry permissions that are required to install the update. It mainly occurs for the windows (O.S.) operating system users. There are so many multiple causes for this Windows Update Error Code 0x80070005 game pass problem & can cause by this security-related error.

Causes of Windows Error 0x80070005 Code Issue:

  • Administrative Issues
  • Access Denied error
  • Windows PC problem
  • Viral Injection
  • Dllregisterserver failed with error code

So, here are some top best tips and tricks for easily fixing and solving this type of Windows Update Error Code 0x80070005 IIS PC problem from your Windows PC permanently. So, just check out this below content,

How to Fix & Solve Windows Error 0x80070005 Code Issue

1. By using the Cmd (Command Prompt) on your Windows PC –

By using the Cmd (Command Prompt)

  • Go to the Start Menu
  • Type ‘cmd‘ & Open it
  • Type “regsvr32 quartz.dll” there & press Enter
  • A Pop-up will open with ‘DllregisterServer in quartz.dll succeeded.’
  • Now press OK & Restart your PC again
  • That’s it, done

It will fix this Windows Update Error 0x80070005 Audio problem from your PC.

2. Install an Automatic Repair Tool on your Windows PC –

Install an Automatic Repair Tool

  • Go & Search for Automatic Repair Tool on the Internet
  • Download it from there
  • Now, Click on ‘RUN‘ & Install it
  • Open it and use the automatic repair tool
  • After finish, close the tab
  • That’s it, done

It will fix this Windows Update Error 0x80070005 Xbox problem quickly from you.

3. Log-on to your Windows PC with Administrator Rights –

Log-on to your PC with Administrator Rights

  • First, Close your PC
  • Shutdown your computer
  • Restart it using Administrator Panel
  • That’s it, done

This will fix this Windows Update error 0x80070005 Outlook problem.

4. Scan your Full Windows for Malware/Virus with Antivirus –

Scan your full PC with a Good Antivirus

Sometimes the file & registry permissions may get changed by malware.

  • Search for a Powerful Antivirus
  • Download it
  • Run it & Scan your full PC
  • After completing, close the tab
  • That’s it, done

By scanning your PC with antivirus may quickly get rid out of this System Restore 0x80070005 problem.

These are some top best tips and tricks to fix this Windows Update Error 0x8007000 Outlook problem from your PC. Hope it will surely help you to get back from this Windows Update 0x80070005 problem.

If you are facing any problem while fixing this type of Windows Update Error 0x80070005 WSL PC problem, then comment down your issue here, so we will fix it soon either in the comment or we solve that problem here in the post.

Troubleshooting HTTP 500.19 Errors in IIS 7

In general, a 500.19 error happens due to invalid configuration data. The IIS configuration system will almost always point to the source of the problem. At the same time, sometimes it is important to examine the “Error Code” field which symbolizes the cause of problem.

Here’s an example of how a 500.19 error appears on an IIS 7.0 server:

500

Let’s talk about some of the causes for 500.19 errors. We will use the ERR.exe tool for looking up the associated error codes (MSDN says it's for Exchange error codes but it works for Win32 error codes and many more.) To use ERR.exe tool and find what an HRESULT error code corresponds to, navigate to the folder where err.exe resides and run command: ERR ErrorCode

Note: Make sure to backup your applicationHost.config file before editing it manually, to avoid any further issuesJ. You can find the detailed instructions here

***************************************

Scenario 1

Error Message:

HTTP Error 500.19 - Internal Server Error

Description: The requested page cannot be accessed because the related configuration data for the page is invalid.

Module: StaticCompressionModule

Notification: MapRequestHandler

Handler: StaticFile

Error Code: 0x800700c1

Requested URL: http://localhost/

Physical Path: C:\inetpub\wwwroot

Logon Method: Anonymous

Logon User: Anonymous

Reason:

The Error Code in the above error message is “0x800700c1” which when translated through ERR.EXE, is

# %1 is not a valid Win32 application.

Solution:

This error normally indicates an attempt to use EITHER

Ø 32-bit executable from a 64-bit process

OR

Ø A corrupt executable

Hence the solution is to make sure that the listed module’s bitness (32bit/64bit) matches the bitness of the application Pool.

***************************************

Scenario 2

Error Message:

HTTP Error 500.19 - Internal Server Error

Description: The requested page cannot be accessed because the related configuration data for the page is invalid in the metabase on the Web server.

Error Code: 0x800700b7

Notification: BeginRequest

Module: IIS Web Core

Requested URL: http://localhost/

Physical Path: C:\inetpub\wwwroot

Logon User: Anonymous
Logon Method: Anonymous

Handler: StaticFile

Config Error: Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'header’

Config File: \\?\C:\inetpub\wwwroot\web.config

Config Source:

21: <customHeaders>

22: <add name="header" value="text/plain" />

23: </customHeaders>

Reason:

This problem essentially happens if there is a duplicate entry for the configuration section setting at a higher level in the configuration (i.e. in parent site/folder’s web.config or applicationHost.config file). The error message itself points out the location of duplicate entries.

Solution:

One should look in the site’s config file and compare it with applicationHost or web.config file at a higher level to check for duplicate entries as pointed by the error message.  You can either remove this entry to make the server run again, or make the entry non-duplicate by changing the collection key.

For example, the above error message was because of the same custom header defined at the IIS root level (applicationHost.config) and at the Default Website (web.config). To solve this, we can

1. Remove this entry from web.config file : <add name="header" value="text/plain" />

OR

2. Add remove OR clear element before this add element:

<remove name="header"/>

OR

<clear />

***************************************

Scenario 3

Error Message:

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

Module: IIS Web Core

Notification: BeginRequest

Handler: Not yet determined

Error Code: 0x8007000d

Config Error: Configuration file is not well-formed XML

Config File: \\?\ C:\inetpub\wwwroot \web.config

Requested URL: http://localhost/

Physical Path: C:\inetpub\wwwroot

Logon User: Not yet determined
Logon Method: Not yet determined

Config Source

3: <system.webServer>

4: </handlers>

5: <remove name="StaticFile"/>

Reason:

That error message goes on to say what exactly is bad about your configuration file, hence you should refer the “Config Error” and “Config Source” sections. This problem occurs because the ApplicationHost.config file or the Web.config file contains a malformed or unsupported XML element.

Solution:

Delete the malformed XML element from the ApplicationHost.config file or from the Web.config file as indicated by the error message.

There are couples of instances that we have come across where the error code remains 0x8007000d, but the cause of issue was interesting.

In one scenario, we had a virtual directory pointing to a UNC share content. This same above 500.19 error was caused because of wrong password specified in the “Connect as..” setting. So make sure to provide the right credentials under “Connect as..” .

Another instance where the error code remained “0x8007000d” but the “Config Error” didn’t complain the mal formed XML, rather was about Configuration section encryption.

HTTP Error 500.19 – Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Module : ConfigurationValidationModule

Notification: BeginRequest

Handler : PageHandlerFactory-Integrated

Error Code: 0x8007000d

Config Error: Configuration section encryption is not supported

Config File: \\?\C:\inetpub\wwwroot\aspnet\web.config

Requested URL: http://localhost/

Physical Path: C:\inetpub\wwwroot

Logon User: Not yet determined
Logon Method: Not yet determined

<identity configProtectionProvider="RsaProtectedConfigurationProvider">

<EncryptedData Type=http://www.w3.org/2001/04/xmlenc#Element

As the error suggests, the error is because IIS7 configuration system only supports per-attribute encryption; it does not support per-section encryption. For more details, refer Section level encryption of ASP.NET settings in IIS 7

***************************************

Scenario 4

Error Message:

HTTP 500.19 - Internal Server Error

Module: IIS Web Core

Notification: BeginRequest

Handler: Not yet determined

Error Code: 0x8007010b

Config Error: Cannot read configuration file

Config File \\?\C:\inetpub\wwwroot\aspnet\web.config

Logon Method: Not yet determined

Reason:

ERROR CODE: 0x8007010b translates to “ERROR_DIRECTORY - The directory name is invalid.”

Solution:

As the error indicates, IIS is not able to find the content directory. For this error, we can run Process Monitor OR use Failed Request Tracing to get the Directory name where it fails. And then verify if that directory name/path is valid or not. If it does exist, then verify the NTFS permissions on that directory for account that is being used to access it.

We have seen this error when the site content is pointing to some Non-NTFS File system. In such cases, it is advisable to test it by placing the content on a Windows/NTFS share.

***************************************

Scenario 5

Error Message:

HTTP Error 500.19 - Internal Server Error
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code: 0x8007052e
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost/
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: Cannot read configuration file
Config File: \\?\UNC\isha2003\wwwroot\web.config

Reason:

The error code in this 500.19 error message is 0x8007052e which indicates:

ERROR_LOGON_FAILURE - Logon failure: unknown user name or bad password.

Solution:

To resolve this error, follow the steps given in the KB 934515

***************************************

Scenario 6

Error Message:

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid. Module DynamicCompressionModule
Notification SendResponse
Handler StaticFile
Error Code 0x8007007e
Requested URL http://localhost:80/
Physical Path C:\inetpub\wwwroot
Logon Method Anonymous
Logon User Anonymous

Reason:

Error Code 0x8007007e is:

ERROR_MOD_NOT_FOUND - The specified module could not be found.

This problem occurs because the ApplicationHost.config file or the Web.config file references a module that is invalid or that does not exist. To resolve this problem: In the ApplicationHost.config file or in the Web.config file, locate the module reference or the DLL reference that is invalid, and then fix the reference. To determine which module reference is incorrect, enable Failed Request Tracing, and then reproduce the problem.

For above specific error (mentioned in this example), DynamicCompressionModule module is causing the trouble. This is because of the XPress compression scheme module (suscomp.dll) which gets installed with WSUS. Since Compression schemes are defined globally and try to load in every application Pool, it will result in this error when 64bit version of suscomp.dll attempts to load in an application pool which is running in 32bit mode.

This module entry looks like:

<scheme name="xpress" doStaticCompression="false" doDynamicCompression="true"
dll="C:\Windows\system32\inetsrv\suscomp.dll" staticCompressionLevel="10"
dynamicCompressionLevel="0" />

Hence to get rid of this problem:

Ø Remove/Disable the XPress compression scheme from the configuration using the command below:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

OR

Ø Add an attribute of "precondition= "64bitness" for this module entry so that it loads only in 64bit application pools

Refer this blog for more details on Preconditions in IIS7

OR

Ø Use a 32bit version of suscomp.dll

***************************************

Scenario 7:

Error Message:

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid. Detailed Error Information

Module IIS Web Core

Notification BeginRequest

Handler Not yet determined

Error Code 0x80070021

Config Error: This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".

Config File \\?\C:\inetpub\wwwroot\web.config

Requested URL http://localhost:8081/

Physical Path C:\inetpub\wwwroot\

Logon Method Not yet determined

Logon User Not yet determined

Config Source

144: </modules>

145: <handlers>

146: <remove name="WebServiceHandlerFactory-Integrated"/>

Reason:

ERROR CODE: 0x80070021 is

ERROR_LOCK_VIOLATION The process cannot access the file because another process has locked a portion of the file.

Solution:

There are usually a few more lines in that error response that points to the exact line in the config file (and hence the locked section) that has the problem. You will either have to unlock that section or not use it in your application’s web.config file.

For e.g., one can lock/unlock handlers/modules sections by either

Ø use appcmd.exe

%windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/handlers

%windir%\system32\inetsrv\appcmd unlock config -section:system.webServer/modules

OR

Ø manually change value from "Deny" to "Allow" for below settings in %windir%\system32\inetsrv\config\ applicationHost.config

<section name="handlers" overrideModeDefault="Deny" />

<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Deny"/>

You can also configure the locking via IIS manager UI.

For more details refer: Locking in IIS 7.0 Configuration

In above error message, the error occurred on the handlers section at:

<remove name="WebServiceHandlerFactory-Integrated"/>”

This usually indicates that ASP.NET is either not installed or has corrupted/incomplete installation because installation of asp.net unlocks that section. Hence if this is the case, one should install asp.net feature from Server Manager (Under Web Server Role in Windows Server 2008 and in Program Features-> Application server in Vista/Windows7). This KB929772 talks about the ASP.NET installation failure reason.

***************************************

Scenario 8

Error Message:

HTTP Error 500.19 - Internal Server Error

Description: The requested page cannot be accessed because the related configuration data for the page is invalid.

Error Code: 0x80070005

Notification: BeginRequest

Module: IIS Web Core

Requested URL: http://localhost

Physical Path: C:\Inetpub\wwwroot

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: Not yet determined

Config Error: Cannot read configuration file

Config File: \\?\ C:\Inetpub\wwwroot\web.config

Reason:

The error code 0x80070005 is:

E_ACCESSDENIED - General access denied error

The “Config error” portion of the error may indicate this too, via message: “Config Error Cannot read configuration file due to insufficient permissions ”

Solution:

Grant Read permission to the IIS_IUSRS group for the ApplicationHost.config file or for the Web.config file indicated in the error message. Even if there is no config file at that location, the worker process identity (and/or the IIS_IUSRS group) needs at least Read access to the directory so that it can check for a web.config file in that directory.  If it’s a UNC share, you need to either run your app-pool as an account that has sufficient permission to the UNC share or configure the virtual directory with a user that has sufficient permission to the share.

If you still see the issue, run the Process Monitor tool, reproduce the error and look for “Access Denied” in the “Result” column. You can then configure the required permissions accordingly.

Other Related Articles:
Troubleshooting HTTP 401.3 errors (Access denied) with Process Monitor

Troubleshooting common permissions and security-related issues in ASP.NET

***************************************

Scenario 9

There’s one intermittent 500.19 error we’ve observed while using Shared Configuration with multiple web servers in a load balanced environment and the configuration files stored on a common UNC file share. In this scenario, if the file share content goes offline, the web server will stop responding. Furthermore, when the file share comes up again, the web server will still not detect it and will fail with a 500.19 error. In order to recover from this situation, you must restart IIS. The solution to this problem is described in this KB

***************************************

Other references:

Error message when you visit a Web site that is hosted on IIS 7.0: "HTTP Error 500.19 – Internal Server Error"

You receive an error message when you try to view a Web page from a Web site that uses pass-through authentication in Internet Information Services 7.0

Troubleshoot IIS7 errors like a pro

load module error 0x800 When trying to import the PnP PowerShell module, I got an error message “Import-Module: The specified module ‘SharePointPnPPowerShellOnline’ was not loaded because no valid module file was found in any module directory”.

You may face this trouble for other PowerShell modules as well. E.g.

  • “import-module : the specified module ‘activedirectory’ was not loaded because no valid module file was found in any module directory.”
  • “import-module : the specified module ‘exchangeonlinemanagement’ was not loaded because no valid module file was found in any module directory.”
  • “import-module : the specified module ‘sqlserver’ was not loaded because no valid module file was found in any module directory.”
Import-Module: The specified module was not loaded because no valid module file was found in any module directory

Solution:

This error is because the PowerShell console or ISE is unable to get the module from given module path’s in the environment variable “PSModulePath”. To fix the issue, You have to make sure your custom module’s path is appended to the PSModulePath environment variable.

Step 1: Get the Path of your custom PowerShell Module.

Make sure you have the custom module installed already. To get the modules installed, Open PowerShell console and type:

Get-module -ListAvailable

This gets all installed modules in your system along with their installed Path. Get the path of your custom module as highlighted, load module error 0x800. In my case, the PnP PowerShell module was installed at “C:\Program Files\WindowsPowerShell\Modules”.

Get-module -ListAvailable

Step 2: Verify if the custom module’s path is added to the “PSModulePath”

As the next step, we have to verify if our custom module’s path is added to the “PSModulePath” variable.

  • Go to System Properties by pressing Windows Key + Pause Break (Or Go to File Explorer >> Right click on “This PC” >> Properties) >> Click on Advanced System Settings >> Click on Environment Variables
  • Pick “PSModulePath” and click on “Edit” button.
    add path to PSModulePath variable
  • Append your PowerShell Module path to this variable. In my case, its “C:\Program Files\WindowsPowerShell\Modules”, load module error 0x800, separated by ; (semicolon). From Load module error 0x800 10 onwards, we have a neat option to add new path. Hit “New” button and add the module’s path there.add to psmodulepath
  • Restart PowerShell ISE or PowerShell console.

This should solve the problem.

Related Posts