Enabling PowerShell Remoting SSL on Windows 7

Hello,
We have been asked to setup PowerShell Remoting HTTPS on our Windows 7 estate. I was just wondering if there is a step-by-step guide (which even includes certificates creation etc.)?
HTTP option was rejected saying it's not secure.
Any help would be highly appreciated.
Regards

Hi,
Here's a few general walkthroughs:
http://blog.powershell.no/2010/03/04/enable-and-configure-windows-powershell-remoting-using-group-policy/
http://www.briantist.com/how-to/powershell-remoting-group-policy/
Here's one that's most likely more on target for what you're after:
https://wprogramming.wordpress.com/2011/07/11/remote-pssession-over-ssl/
It's unlikely that you'll find something that will hold your hand the entire way through, but a combination of these should get you moving in the right direction.
Don't retire TechNet! -
(Don't give up yet - 12,830+ strong and growing)

Similar Messages

[Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.
Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force
Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
the memory via the PowerShell command below:
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.
You can get more information regarding Remote Troubleshooting by below link:
about_Remote_Troubleshooting
If you need further assistance, welcome to post your questions in the
RDS forum.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
ot process the request. It cannot determine the content type of the HTTP response from the destination comput
er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
many security groups or in my case because of the SidHistory attribute.
The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
If the keys does not exists you can create them, be sure to use the DWORD type.
I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

[Forum FAQ] Introduce Windows Powershell Remoting

This article will introduce three methods of Windows Powershell Remoting:
Method 1: WMI
Remoting Cmdlet: Get-WMIObject
Protocols: WMI/RPC/DCOM
Port: Random port
Data Encryption: Clear text
Note: No need of the WinRM’s installation and configuration
Method 2: PowerShell Remoting Commands
Remoting Cmdlet: Invoke-Command
Protocols: HTTP (wsman), MIME, SOAP, XML
Port: 5985
Data Encryption: Encrypted
Note: Support any cmdlets in the parameter scriptblock, however, need the computer install WinRM, and also need to configure the WinRM on the remote computer.
Method 3: PowerShell Remoting Interactively
Remoting Cmdlet: Enter-PSSession
Protocols: HTTP (wsman), MIME, SOAP, XML
Port: 5985
Data Encryption: Encrypted
Note: Support any cmdlets, all cmdlets you type are executed as if they were typed on the console of the remote computer. However, need the computer install WinRM, and also need
to configure the WinRM on the remote computer.

2. Powershell remote in the same domain with WinRM installed: Invoke-Command, Enter-PSSession
2.1 PowerShell Remoting Commands: Invoke-Command
If you only have a couple of commands to execute on the remote computer in the same domain, you can use the
Invoke-Command cmdlet.
For example: Server1 want to remote manage Server2
1) Enable powershell remoting on Server2
Launch Windows Powershell as “Run as Administrator” on server2, and run:
Enable-PSRemoting –Force
Note:
In Server 2012 (but not Windows 8), PowerShell remoting is enabled by default, so you don't need to do anything.
2) Run invoke-command on server1
Invoke-Command -ComputerName server2 -Credential domain\username -ScriptBlock {get-process}
If the user account run with Powershell has the admin permission, there is no need to specify the credential parameter.
The script above will run the cmdlet “get-process” on server2, and a temporary connection will be built, the result returned to server1, and the connection broken.
If you want to run powershell script .ps1 file on server2, however, this script is stored on server1, you can achieve as below:
Invoke-Command -ComputerName server2 -Credential domain\username -FilePath d:\1.ps1
2.2 PowerShell Remoting Interactively: Enter-PSSession
To work interactively, use
Enter-PSSession to connect to a remote session, all the cmdlets you typed in your local console is executed on the remote system until you leave the remote session by using
Exit-PSSession.
After configure the WinRM on server2, you can run
enter-pssession on server1 (Figure 3):
Figure 3: remote with enter-pssession
2.3 Powershell remote with Pssession: New-Pssession
Whenever you use Windows PowerShell Remoting with the ComputerName parameter, a temporary session is created for you and used only for this particular command. Once the command
completes, the session is automatically closed.
If you start to access remote systems more often or would like to keep the session state, a more efficient way is to create sessions yourself and keep them around until you no longer
need them. To achieve this, instead of specifying the parameter computername, you can also specify Pssession in the Session parameter of the cmdlets
invoke-command and enter-pssession (Figure 4).
Figure 4: persistent session
If there is no need to use the Pssession, you can use the cmdlet
Remove-PSSession to close the session.

Remote Powershell - Access Denied? Windows 8.1

I want to be able to connect to my PC from anywhere around the world. Don't ask why. As such I have forwarded my private IP :192.168.... to my public
IP (ports : 22,23, 3389,5975,5976). Of course my public IP changes constantly so i also have a DNS Updater with a name : nameofmyhost.somehing.com .
I have been able to connect using Remote Desktop connection from my phone, tablet, other PC's, using that nameofmyhost.somehing.com.
However this is a desktop connection. I want a command connection as well (Powershell), no Telnet, and no SSH. I have configured WinRm, and tried powershell
remoting using enter-pssesion nameohmyhost.somehing.com. Problem is that it's always Access Denied.
I want to be able to connect remotely via powershell to my PC at any times.
Yes i did quickconfig the winrm, i did add to TrustedHosts, but i still can't connect. Someone please tell me if what i am trying is even possible,
and if it is, please give me a COMPLETE TUTORIAL FOR DUMMIES on how to make it happen.
Thanks

You can verify the availability of WinRM and configure a PowerShell for remoting by following these steps:
1. Start Windows PowerShell as an administrator by right-clicking the Windows PowerShell shortcut and selecting Run As Administrator.
2. The WinRM service is confi gured for manual startup by default. You must change the startup type to Automatic and start the service on each computer you want to work with. At the PowerShell prompt, you can verify that the WinRM service is
running using the following command:
get-service winrm
The value of the Status property in the output should be “Running”.
3. To configure Windows PowerShell for remoting, type the following command:
Enable-PSRemoting –force
In many cases, you will be able to work with remote computers in other domains. However, if the remote computer is not in a trusted domain, the remote computer might not be able to authenticate your credentials. To enable authentication, you need to add the
remote computer to the list of trusted hosts for the local computer in WinRM. To do so, type:
winrm s winrm/config/client '@{TrustedHosts="RemoteComputer"}'
Here, RemoteComputer should be the name of the remote computer, such as:
winrm s winrm/config/client '@{TrustedHosts="CorpServer56"}'
When you are working with computers in workgroups or homegroups, you must either use HTTPS as the transport or add the remote machine to the TrustedHosts configuration settings. If you cannot connect to a remote host, verify that the service on the remote host
is running and is accepting requests by running the following command on the remote host:
winrm quickconfig
This command analyzes and configures the WinRM service.
To use Windows PowerShell remoting features, you must start Windows PowerShell as an administrator by right-clicking the Windows PowerShell shortcut and selecting Run As Administrator. When starting PowerShell from another program, such as the command prompt
(cmd.exe), you must start that program as an administrator
From W. Stanek: Windows PowerShell 2.0 Administrator’s Pocket Consultant

Enabling Remote Desktop On Windows 7 Home Premium

So, I'm trying to set up a remote desktop connection on a computer. I already opened the ports necessary to do so (3389) and when I go to configure the remote settings through the system in control panel, Remote Desktop isn't there.
I tried enabling it through editing the registry (even though I knew it wouldn't work) and tried numerous other things in efforts to get it working. No matter what I do, nothing seems to work in enabling the remote desktop options to show up like it does in the next picture.Anything to help get this remote desktop to work would be greatly appreciated.
This topic first appeared in the Spiceworks Community

follow this document for Windows 7 backup
http://windows.microsoft.com/en-us/windows/back-up-programs-system-settings-files#1TC=windows-7
how much space at target volume? external HDD? USB pen drive?
i suggest using external HDD, USB pen drive will takes forever
or you can also try using 3rd party application, but its our own risk and fully support comes from manufactured

Listing RDS 2012 R2 collections from powershell remote fails

I'm trying to list different informations of a RDS server farm => from a remote client PC <=
I do following but when typing the last command - I get an error.
Knowing that that same command runs correctly when launched from an RDS server
enter-pssession RDS-SERVER-XYZ.contoso.net
import-module remotedesktop
get-command -module remotedesktop
Get-RDSessionCollection -ConnectionBroker RDS-BRK-1.contoso.net
=> fails with message :
Cannot index into a null array.
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\remotedesktop\Utility.psm1:54 char:9
+     if ($_script_resource[$Id])
+         ~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : NullArray
Cannot index into a null array.
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\remotedesktop\Utility.psm1:54 char:9
+     if ($_script_resource[$Id])
+         ~~~~~~~~~~~~~~~~~~~~~~
     + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
     + FullyQualifiedErrorId : NullArray
Get-RDSessionCollection :
   + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
     + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-RDSessionCollection
Listing RDS 2012 R2 collections from powershell remote fails / same commandlet from local RDS serevr works fine
Am I missing something ?
MCTS Windows Server Virtualization, Configuration

Are the Windows Remote Management rules enabled on the inbound firewall of the RDSH server?
If you are running multiple roles on the RDSH server you may need to increase the size of the memory available for powershell remoting.
Run Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000 with powershell as an admin and reboot.
HTH,
JB

Using drag and drop in remote desktop on windows server 2008

we running an application on windows server 2008 terminal services .. this application was support drag and drop functionality .. i understand that terminal services on windows 2008 is supported to drag and drop but is not happening !! even when i run remote desktop connection on this server the drag and the drop is not working !
i need to enable the drag and drop for windows 2008 terminal services ..
Thanks in advance

Hello Ayman,
If your requirement is to drag and drop files between local and remote sessions, Danny is right. Drag-and-drop feature is not supported in Windows Server 2008-based Terminal Server, which is a by-design behavior hard-coded in the current version of the Remote Desktop Protocol.
As a workaround, I recommend you to use copy-and-paste function instead of drag-and-drop. To enable the copy-and-paste between local and remote session, please enable the clipboard redirection in Windows Server 2008-based RDC. (In Windows Server 2003 environment, local drive redirection is needed.)
Hope it helps. Thanks.
Best Regards,
Lionel Chen

How do I show remote printers in Windows 2012 RDWEB?

Hi everyone,
I have setup an Windows 2012 RDS host and am able to access it externally by using https://remote.domain.com/rdweb.
Therefore I can log in and launch remote apps.
Local printers get redirected, but I do not seem to be able to see the remote printers on the RDS server.
The printer is installed and it is installed on the server.
What if I want to print on the server printer rather than my own printer?
How to get to show the printers in the RDWEB page?
I do not get control panel, select device and printers here.
Can someone enlighten me on this?
Thanks very much.
Regards
Ipnotech

Hi,
Any takers for this question?
When I use internet explorer to access the Windows 2012 r2 RDS server by typing https://remote.domain.com/rdweb, I get to logon and can see all my published apps and launch them.
But when I print from a remote app I can only see my own redirected printers I cannot see the network printer which is installed on the server.
I tried to change group policy under Computer Configuration/Administrative Templates/Windows Components/Remote Desktop Services/Remote Desktop Session Host/Printer Redirection and set:
Do not set default client printer to be default printer in a session ENABLED
Use Remote Desktop Easy Printer Driver first ENABLED
Redirect only the default client printer ENABLED
Then I run a gpupdate /force on the RDS host to apply the policy to the server.
When I connect remotely from a Windows 7 client using IE and lets say I launch the wordpad remote app I can only see my client printers not the server printers.
This seems to work if I RDP into the server with mstsc.exe but not using RDWEB.
Does anyone know about this?
Thanks and regards
Ipnotech

Powershell expert help needed in powershell remoting C#

im trying powershell remoting for some specific operatons on a remote computer and using wsman for the connection options.
WSManConnectionInfo connectionInfo = new WSManConnectionInfo(false, sharepointHost, 5985, "/wsman", "http://schemas.microsoft.com/powershell/Microsoft.PowerShell", new System.Management.Automation.PSCredential(admindata.Domain + "\\" + admindata.Admin, Helper.ToSecureString(admindata.Password)));
connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Credssp;
connectionInfo.ProxyAuthentication = AuthenticationMechanism.Negotiate;
normally it works fine but sometimes just before the runspace.open command is executed, the machine is pinging with its hostname and when the runspace.open is called, the machine doesnt ping with its hostname and my poweshell code fails with exception "machine
not reachable"
then after 1 or 2 restarts it pings back and again at runspace.open it doesnt ping. please make a note that um using credssp as authentication mechanism so whenever i enable or disable WSMancredssp inshort whenever i run either commands in my powershell,
the remote machine is again pinging with its hostname.
then after some hours it runs with no disturbance. and i dont have to bother about WSMancreddsp also
can any one tell me what could be the possible reason for it, is it with my local system or the remote system. Does it has anything to do with me enabling the Credssp thing???
please help me guys, im totally lost here.
PS: im running these commands on sharepoint server

Hi,
I would like suggest you refer to the below link about running powershell within C#:
How to call Powershell Script function from C# ?
http://social.msdn.microsoft.com/Forums/is/csharpgeneral/thread/faa70c95-6191-4f64-bb5a-5b67b8453237
http://stackoverflow.com/questions/527513/execute-powershell-script-from-c-sharp-with-commandline-arguments
How to run PowerShell scripts from C#
http://www.codeproject.com/Articles/18229/How-to-run-PowerShell-scripts-from-C
Hope this helps.
Regards,
Yan Li
Cataleya Li
TechNet Community Support

How do I enable VNC remote login on Snow leopard?

I am setting up a Mac Mini running SL for my in-laws in NYC. I have been using Chicken of the VNC to access their Windows machine to keep it running with all of the viruses and malware they continually download.
I had found instructions on how to enable OSX's built in VNC access:
http://www.dssw.co.uk/blog/2007/05/14/a-vnc-server-is-included-in-mac-os-x-104/
but when trying to set it up I find that SL's systems sharing preferences have changed and I do not see VNC on the list...
What do I do?

Do I need to enable BOTH remote management AND screen sharing and if so which one do I enable first?
What users need to be defined in "Allow Access"? All Users or just the under accounts defined on the host machine?
In Remote management Under "Computer Settings" which should I have checked: ... only "VNC viewers may control screen with password"? (and of course enter password...) Does anything need to be filled into the "Computer Information fields .. and if so what?
Under "Screen Sharing" what users need to be defined in "Allow Access"? All Users or just the under accounts defined on the host machine?
Again in "Computer Settings" which should I have checked: ... only "VNC viewers may control screen with password"? (and of course enter password...)
Thanks... this is the only thing I have yet encountered on a Mac that is more difficult to get working than it is on a WinDoze machine.....

Issues using SharePoint PowerShell cmdlets using PowerShell Remoting

We are having an issue with the SharePoint 2010 management cmdlets inside of a PowerShell Remoting session.
Here is a example code output (stripped of company-specific data):
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\> $Server = "server.domain.msd"
PS C:\> $Credential = Get-Credential "domain\admin"
PS C:\> $Session = New-PSSession -ComputerName $Server -Credential $Credential -Authentication "CredSSP" -UseSSL -SessionOption $(New-PSSessionOption -SkipCNCheck -OperationTimeOut 0 -OpenTimeOut 10000)
PS C:\> Enter-PSSession $Session
[server.domain.msd]: PS C:\> Add-PSSnapin "Microsoft.SharePoint.PowerShell"
[server.domain.msd]: PS C:\> New-SPUser -UserAlias "domain\spadmin" -sitecollectionadmin -web "http://sharepoint"
New-SPUser : You need to be a site collection administrator to set this property.
+ CategoryInfo : InvalidData: (Microsoft.Share...SPCmdletNewUser:SPCmdletNewUser) [New-SPUser], SPExcepti
on
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewUser
[server.domain.msd]: PS C:\> whoami
domain\admin
[server.domain.msd]: PS C:\>
However if I run the command on the remote system inside of an RDP session it works fine:
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\> Add-PSSnapin "Microsoft.SharePoint.PowerShell"
PS C:\> New-SPUser -UserAlias "domain\spadmin" -sitecollectionadmin -web "http://sharepoint"
UserLogin DisplayName
i:0#.w|domain\... DOMAIN\spadmin
PS C:\> whoami
domain\admin
PS C:\>
This looks like it has something to do with WinRM not being an elevated shell, because when I use the SharePoint API inside of WinRM I need to use RunWithElevatedPrivileges. Does anyone know of a way around this limitation?

Hye i found a way to run sharepoint cmdlets from remote computer on this blog. Actually we need to use credssp authentication mechanism.
hope it helps others.
http://www.liberalcode.com/2013/04/running-sharepoint-cmdlets-from-remote.html

I am trying to remote into a Windows Server 2003 from a Windows 7 machine and having issues

I am trying to remote into a Windows Server 2003 from a Windows 7 machine. It says "The terminal server has exceeded the maximum number of allowed connections".
My first stop in trying to solve this problem was here:
[URL="http://www.howtogeek.com/howto/windows/command-line-hack-for-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"]howtogeek.com[/URL]
And it says:
[I]
[INDENT]This problem happens because Windows only allows two remote terminal services connections when you are in administrative mode, and you’ve either got two people already on that server, or more likely, you’ve got a disconnected session that still thinks
it is active.
The problem with this error is that you have to actually get on the server console to fix the problem if the server isn’t in a domain. ([B]If you are in a domain, then just open Terminal Services Manager and log off or disconnect the sessions[/B])[/INDENT][/I]
So it seems to suggest that all I have to do really is to run the Terminal Services Manager but I cannot find it.
This web site from mssqltips.com [URL="http://www.mssqltips.com/sqlservertip/1981/remote-desktop-error-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/"](click here)[/URL] says all I need to do is first execute "mstsc /
admin" from the command line. But, when I do that, I get a message when I try to remote to the server, that says this: "To log on to this remote console session, you must have administrative permissions on this computer".
So, what now? What do you suggest?

Hi Bobby,
Yes, it is by design. By default, Windows Server only accepts two concurrent administrative sessions (Administrative Mode). It means that only two administrators can work on the server at
the same time.
If you would like more concurrent sessions, you need to purchase RDS CALs, install Terminal Services related server roles with proper configurations on the server.
Remote Desktop for Administration (server 2003)
http://technet.microsoft.com/en-us/library/cc785186(v=ws.10).aspx
What Is Terminal Services?
http://technet.microsoft.com/en-us/library/cc782486(v=ws.10).aspx
Terminal Services Configuration
http://technet.microsoft.com/en-us/library/cc787078(v=ws.10).aspx
Purchase client access licenses
http://technet.microsoft.com/en-us/library/3660ac5a-7468-48d3-b7e8-5529de8fb6c5
Thanks.
Jeremy Wu
TechNet Community Support

Can ARD 3 be used for users who want to remote into a windows based server?

I have a couple users at the company I work at who will need to be able to remote into our Windows Server. These users all have Macs and will have to go about remoting in differently. I have done some research on Apple Remote Desktop but i am unsure if it fits my users needs. If I have someone download and install this software on a mac, will they then be able to remote into a windows based server using an IP address? that is my goal in mind could get some help on this one I'd appreciate it.
Thanks,
- Rich

I'm referring to what windows can do via Remote Desktop connection.
You open up the RDC dialog box, enter an external IP address (if working remotely) or a server name if working internally and connect right to the machine. Ideally i want my users to be able to log into our terminal server and be able to use a program remotely. they will have to log on to this server with company credentials. Basically from a mac, connecting up to a Windows Server and remotely logging into it to perform tasks.
I'm really just trying to find an easy way to do this for my user's with MAC's since it is not as straightforward as in windows. I cannot test anything out at home since i do not own a mac so i come to the community to see if you guys have had the same kind of situation before.
ARD was the first peice of software that looked like it might fit my needs but if it doesn't is there anything out there? is it for free or for a cost? any help is greatly appreciated. Thanks.
- Rich

Windows XP see blank screen when remote desktop to Windows 7 with fast user switching disabled

All computers are in workgroup environment, no AD.
Windows 7 pro are configured with fast user switching mode disabled so that only one login session can run at a time. When a Windows 7 machine remote desktop to another Windows 7 machine, the remote desktop 'server' will give 30 seconds count-down for the
console logged in user to accept remote connection, or when timeout expires it kicks out the console logged in user. This is completely ok.
This become a problem when a Windows XP rd client try to remote desktop to these Windows 7 machines, Windows XP see a blank screen if the remote Windows 7 machine has a user logged in, as it is waiting for the user to log off first. This is not desirable
as our administrators want the console session to be logged out automatically if they (administrators) want to remote desktop in.
Is this a configuration problem? Is this a OS design, can't be changed?
Valuable skills are not learned, learned skills aren't valuable.

Hi,
As I know, for RDP session in Windows 7, you don't need to configure the fast user switch option disabled. Windows 7 doesn’t support multiple Remote Desktop sessions by design, that means only one RDP session at a time.
I remote into my Windows 7 machine (which has a user logged in) from my XP machine, all work fine, the user logged in Windows 7 machine is automatically "kicked off".
May I ask a question? Does this issue happen in all XP machines? If you leave Windows 7 machine started and no user logged in, the RDP session in Windows XP established quickly?
I would suggest you keep latest drivers graphic card and latest updates paches for both Windows XP (Windows XP has come to its end of the lifecycle)and Windows 7.
Yolanda Zhu
TechNet Community Support

How to enable JIT debugging on my Windows 7 (64 bit) computer? I keep getting different Errors popping up on my computer about debugging different programs and that JIT debugging must be enabled!

How do I enable JIT debugging on my Windows 7 (64 bit) computer? I keep getting different Errors popping up on my computer and the latest one says when I attempted to watch a DVD video with VLC media player but this isn't the first error this week saying
that JIT debugging must be enabled and I don't know how to do that : ( "Microsoft Visual C++ Runtime Library" Assertion Failed! Program C:\Program Files (x86) VideoLAN\VLC\vlc.exe File: vm.c
Line: 1765
Expression: pgcit != NULL
For information on how your program can cause an assertion failure, see the Visual C++ documentation on asserts.
(Press Retry to debug the application- JIT must be enabled)

Hi Rhondavas77,
To enable/disable Just-In-Time debugging
On the Tools menu, click Options.
In the Options dialog box, select the Debugging folder.
In the Debugging folder, select the Just-In-Time page.
In the Enable Just-In-Time debugging of these types of code box, select or clear the relevant program types:
Managed, Native, or Script.
To disable Just-In-Time debugging, once it has been enabled, you must be running with Administrator privileges. Enabling Just-In-Time debugging sets a registry key, and Administrator privileges are required to change that key.
Click OK.
More information is here.
http://msdn.microsoft.com/en-us/library/k8kf6y2a(v=vs.85).aspx
Best Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Enabling PowerShell Remoting SSL on Windows 7

Similar Messages

Maybe you are looking for