handler "extensionlessurlhandler-integrated-4.0" has a bad module "managedpipelinehandler" in its module list
You need to install ASP.NET 4.5 and Application Initialization.
You can do this via the Server Manager,
- Manage > Add Roles and Features
- Next > Next > Next
- Under Server Roles expand "Web Server (IIS)" > "Web Server" > "Application Development"
- Check the following
- Application Initialization
- Asp.net 4.5
- Next > Next > Install
That's it, your done.
This can be caused if you've changed your administrative account user to improve security on a server.
In order to resolve this issue you will need to stop the max view services in this order:
Then edit cimserver_planned.conf in your maxview storage manager, default path is:
C:\Program Files\Adaptec\maxView Storage Manager\pegasus\cimserver_planned.conf
open with text editor and alter the line from
It may look something like this:
save and exit the conf file.
Now start the maxview Storage Manager services in this order:
Now you can login with your admin account correctly.
This can occur with with to many rdp connection attempts, someone may be trying to break into your computer/server.
Check your resource monitor network usage, if you see many connections (10, 20+) with svchost.exe (termsvcs) then someone is attempting to break into the system.
Its best practice to limit RDP connections to specific IP addresses or via a VPN to prevent this. However, in some cases this may not be possible, so you may change the port number which may help mitigate the attack.
WARNING, Incorrectly editing your registry can cause your system to become non functional. Proceed at your own risk.
open regedit, and go to "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp" then select the PortNumber REG_DWORD entry and change the value data in Decimal to the new port number. Restart the service or system to make the change active.,
It can also be cause when a windows servers is running on vmware or hyper-v and in some cases with a stand alone server where hardware has changed. In most cases this error starts after virtual machine resource changes, or some windows updates.
On the computer you are connecting to...
Then go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
Then choose Require use of specific security layer for remote (RDP) connections
Enable > then choose Security Layer: RDP
Reboot the system.
note: I am not actually sure of the actual cause of this error, if someone has some details please share them below.
So you go to login to via RDP to a server, workstation or remote PC and you get this error:
Not to worry, here is the fix as well as the why.
First run windows update on your local system and try again.
Quick fix: (not secure)
- Use the Windows+R key to open the Run Command. (If you keyboard lacks the windows key you can use Ctrl+Alt+DEL, open task manager, then click file and "Run".)
- In the run command type in gpedit.msc which will open the Local Group Policy Editor.
- Expand Computer Configuration > Administrative Templates > System > Credentials Delegation.
- Update the Encryption Oracle Remediation policy to Enabled, then change Protection level to Vulnerable.
- After doing this it is advisable to update your remote system and switch these settings back.
Proper fix: (secure)
Update the remote server, in some cases the remote server may show that is it up to date in which case you may have a compromised system and will need to follow the following steps in order to force the update after which you should do a full scan on the system for potential malware.
After the May 2018 update RDP no longer connects by default to a remote system that is not running the CredSSP update.
Open the OSD display by pressing one of the buttons next to the power,
Now, press buttons in order from left to right: #5, #3, #5, #5, #3, #5, #5
You should now have "Refresh Num Rate" selected, we need to turn this off.
Press #3, #5
Now press #2, #5, #5,
We are now selected on "Game Mode", we need to save the settings we just changed so the display does not reset next time it switches modes or is turned off and back on.
Select your save mode then press #3 to save.
The framerate should now be turned off and should not turn back on.