Application error 1000 mstsc

application error 1000 mstsc

Log Name: Application Source: Application Error Date: 11/6/ AM Event ID: Task Category: () Level: Error. Faulting application name: sprers.eu, version: , If I guess correctly, you will get error from wsl --version because most. It seems like RDM hangs right after opening a RDP session. A possible workaround in order to prevent the application from crashing is to minimize and maximize.

Application error 1000 mstsc - lie

@ Jeff, those packages are installed on the machine.
Apologies, there are actually event logs in Event Viewer. I was looking at the wrong machine at the time. Here are the entires.


Log Name: Application
Source: .NET Runtime
Date: 14/07/ PM
Event ID:
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: laptop01
Description:
Application: sprers.eu
Framework Version: v
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c, exception address 77DC1C76

Log Name: Application
Source: Application Error
Date: 14/07/ PM
Event ID:
Task Category: ()
Level: Error
Keywords: Classic
User: N/A
Computer: laptop01
Description:
Faulting application name: sprers.eu, version: , time stamp: 0xcdf81
Faulting module name: sprers.eu, version: , time stamp: 0xecd6
Exception code: 0xc
Fault offset: 0xc76
Faulting process id: 0x3a0
Faulting application start time: 0x01d2fc2df72d5b4a
Faulting application path: C:\Program Files (x86)\Devolutions\Remote Desktop Manager Free\sprers.eu
Faulting module path: C:\windows\SYSTEM32\sprers.eu
Report Id: fbaedea-d0df9a3e2edf
Faulting package full name:
Faulting package-relative application ID:



Log Name: Application
Source: Windows Error Reporting
Date: 14/07/ PM
Event ID:
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: laptop01
Description:
Fault bucket , type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: sprers.eu
P2:
P3: cdf81
P4: sprers.eu
P5:
P6: ecd6
P7: c
P8: c76
P9:
P

Attached files:
C:\Users\testuser\AppData\Local\Temp\sprers.eu

These files may be available here:
C:\Users\testuser\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_RemoteDesktopMan_95fabbec7dc22d9e75af8edea_86d4ad15_23ff7a32

Analysis symbol:
Rechecking for solution: 0
Report Id: fbaedea-d0df9a3e2edf
Report Status: 0
Hashed bucket: e98fbfbbb




Log Name: Application
Source: Application Error
Date: 14/07/ PM
Event ID:
Task Category: ()
Level: Error
Keywords: Classic
User: N/A
Computer: laptop01
Description:
Faulting application name: sprers.eu_WbioSrvc, version: , time stamp: 0x
Faulting module name: unknown, version: , time stamp: 0x
Exception code: 0xc
Fault offset: 0x
Faulting process id: 0x22d0
Faulting application start time: 0x01d2fc4b68c
Faulting application path: C:\windows\system32\sprers.eu
Faulting module path: unknown
Report Id: abbeea-d0df9a3e2edf
Faulting package full name:
Faulting package-relative application ID:



Log Name: Application
Source: Windows Error Reporting
Date: 14/07/ PM
Event ID:
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: laptop01
Description:
Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: sprers.eu_WbioSrvc
P2:
P3:
P4: StackHash_
P5:
P6:
P7: PCH_84_FROM_BRCMSENSORADAPTER+0xD58
P8: c
P9:
P

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_sprers.eu_Wbio_de79fca3be8aadc4a9bbd71df5_06df_

Analysis symbol:
Rechecking for solution: 0
Report Id: abbeea-d0df9a3e2edf
Report Status:
Hashed bucket:




Log Name: Application
Source: Application Error
Date: 14/07/ PM
Event ID:
Task Category: ()
Level: Error
Keywords: Classic
User: N/A
Computer: laptop01
Description:
Faulting application name: sprers.eu, version: , time stamp: 0xf
Faulting module name: sprers.eu, version: , time stamp: 0x
Exception code: 0xc
Fault offset: 0xf1c00
Faulting process id: 0x1f8c
Faulting application start time: 0x01d2fc3f37ee96f5
Faulting application path: C:\windows\system32\sprers.eu
Faulting module path: C:\windows\SYSTEM32\sprers.eu
Report Id: bbedceea-d0df9a3e2edf
Faulting package full name:
Faulting package-relative application ID:

Connect using RDP

Connect to target devices directly from your desktop using any standard RDP client application, such as MSTSC or Connection Manager, to benefit from a native user experience.

To connect using a smart card:

  • Smart card drivers must be installed on the PSM machine
  • The smart card must include a valid certificate
  • Privilege Cloud must be configured with LDAP integration

There are two ways to connect using RDP:

  • Create an RDP&#;file for each account you want to access, and then double-click the file to connect.

    If you have multiple accounts that you access regularly, we recommend that you create an RDP file for each, after which you will be able to connect to all of your accounts without additional configuration. For details, see Create an RDP&#;file

  • Connect using any standard RDP&#;client.

    Configure the RDP&#;client whenever you want to access the target account. For details, see Connect using a standard RDP&#;client

    You can also see Connect using MSTSC or Connect using Connection Manager if you are using one of these specific clients.

In either case, you can connect without providing connection details in advance, as described in Connect using RDP&#;without providing details in advance.

Create an RDP&#;file

There are two ways to create an RDP&#;file:

  • Manually, as described in the procedure below.
  • Save it from the RDP&#;client UI. You can make the configurations in the UI&#;and then save them as a file. For details, see Connect using a standard RDP&#;client

Perform the following procedure for each target account.

To create an RDP&#;file manually:

  1. Create an RDP file in the following format:

  2. Configure the following RDP settings:

    Example 1: Windows server on RDP protocol

    To connect to a Windows server with the address of , with the user admin and with the RDP protocol, use the following configuration in the Start Program setting:

    &#;
    Example 2: Windows server with domain user and RDP Protocol

    To connect to a Windows server with the address of , which belongs to the domain sprers.eu, with the domain user domainadmin and with the RDP protocol, use the following configuration in the Start Program setting:

    &#;

    &#;

    &#;

    To allow the connection, a domain account with the address of sprers.eu and the username domainadmin must pre-exist in Privilege Cloud.

    Example 3: Unix server with the SSH protocol

    To connect to a Unix server with the address of , with the user root and with the SSH protocol, use the following configuration in the Start Program setting:

    &#;
    Example 4: Unix server with the WinSCP client

    To connect to a Unix server with the address of , with the user root and with the WinSCP client, use the following configuration in the Start Program setting:

    &#;
  3. To connect using a smart card, add redirectsmartcards:i:1 to the RDP&#;file.
  4. To connect to the target account, double-click the file.

Connect using a standard RDP&#;client

If you are using a standard RDP&#;client (that is neither MSTSC nor Connection Manager), You can configure a single RDP&#;file to connect through Privilege Cloud, which includes the target machine details in advance.

To connect using RDP without configuring the details in advance, see Connect using RDP&#;without providing details in advance.

To connect using RDP&#;(configure details in advance):

Configure the settings of the RDP&#;client as described in RDP&#;settings.

Connect using MSTSC

This procedure describes how to connect to a target device, through Privilege Cloud, specifically using MSTSC.

To connect using MSTSC:

  1. Open the MSTSC client.

    You can also execute MSTSC through the command line using:

  2. In the Computer field, enter the address of the PSM server, through which you will establish the connection. The PSM address can be entered either as a DNS name, or as an IP address in IPV4 format.

    In an environment with load balanced PSMa, specify the address of the PSM load balancer.

  3. Expand Show Options, and do the following:

    1. In the User name field, enter your CyberArk user name.

      If you do not configure your username, you will be prompted for it when the connection is made. You will also be prompted for your password.

    2. Click the Programs tab, and select Start the following program on connection
    3. In the Program path and file name field, enter the connection details to PSM. For details, see RDP&#;settings.
    4. If you are using smart card authentication, click the Local Resources tab, and select Smart cards.
  4. Click Connect.

Connect using Connection Manager

This section describes how to connect to a target device, through Privilege Cloud, specifically using Connection Manager, by configuring the Connection Manager with the target machine details in advance.

To connect using RDP without configuring the details in advance, see Connect using RDP&#;without providing details in advance.

To connect using Connection Manager (configure details in advance):

  1. Open Connection Manager application on your desktop and create an entry for the target device.

    Give each entry a meaningful name to indicate the target device details.

  2. Set the Remote machine address to the address of the PSM server through which you want to establish your connection.

    The PSMaddress can be entered either as a DNS name, or an IP address in IPV4 format.

    In an environment with load balanced PSMs, specify the address of the PSM load balancer.

  3. To connect using a smart card, enable smart card redirection in the connection manager setting.
  4. Enter your Privilege Cloud credentials.

    If you do not configure the log on credentials, you will be prompted for them when the connection is made.

  1. Configure the RDP&#;settings, as described in RDP&#;settings.

Connect using RDP&#;without providing details in advance

You can connect using any standard RDP&#;client or an RDP&#;file without providing details about your target machine in advance.

To connect using an RDP&#;file, a standard RDP&#;client, or Connection Manager (without providing details in advance)
&#;
  • To use this option with NLA, you must use a username that contains the login pattern configured by your Administrator under the PSMLoginPattern parameter. For details, see PSM basic parameters file .
  • When connecting with PKI authentication in NLA, authentication is performed with the smart card certificate, but you still must include the login pattern in the usename field to support this capability.
  1. Configure the following settings:

    Setting RDP Parameter Type Description
    full address s

    The address of the PSM server through which you want to establish your connection.


    The PSM address can be entered either as a DNS name, or an IP address in IPV4 format.

    In an environment with load-balanced PSMs, specify the address of the PSM load balancer.

    alternate shell s

    Only value the PSM parameter ("psm ").

    There must be a space after psm.

    username s

    Enter your CyberArk user name, according to the authentication process required in your environment.

    If you do not configure your user name, you will be prompted for it when the connection is made. You will also be prompted for your password.

    Note:&#;We do not recommend saving your password.

    Example:

  2. To connect using a smart card, add redirectsmartcards:i:1 to the RDP&#;file.
  3. When you connect to the target, after you enter your authentication details, you are prompted for your connection details.
To configure MSTSC to connect to the target machine without using the Programs tab without providing details in advance)
&#;

You cannot use this option if NLA is enabled in your environment.

  1. Open MSTSC.

    &#;

    You can also execute MSTSC through the command line using:

    MSTSC /v:<PSM server address>

  2. In the Remote Desktop Connection window, in the Computer field, enter the address of the PSM server through which you will establish the connection.

    The server address can be entered either as a DNS name, or as an IP address in IPV4 format.

    In an environment with load-balanced PSMs, specify the address of the PSM load balancer.

  3. Open Show Options, and in the User name field, enter "psm " followed by your CyberArk user name, according to the authentication process required in your environment.

    If you do not configure your user name, you will be prompted for the user name and password when the connection is made.

    &#;
    • We do not recommend saving your password locally.
    • There must be a space after psm.
  4. If you are using smart card authentication, click the Local Resources tab, and select Smart cards.

  5. When you connect to the target, after you enter your authentication details, you are prompted for your connection details.

RDP&#;settings

The following settings are relevant for all types of RDP&#;connections.

Settings Description
full address

The address of the PSM server.

Get this information from your admin.

alternate shell

  • target-user The name of the user used to log on to the target device.

    When using a domain account, use the following format:

    [email protected]

    When using a shared account to connect to vCenter machine, use the following format:

    [email protected]

  • target-address The address of the target system. As defined in the account address setting.

    Use one of the following formats:

    • IPv4 – For example,
    • IPv6 – For example,
    • DNS – For example, ‘myhost’
  • connection-component The type of the connection that will be established with the target device.

    Get this information from your admin.

username

Enter your CyberArkuser name, according to the authentication process required in your environment. If you do not configure your user name, you will be prompted for it when the connection is made. You will also be prompted for your password.

Note: We do not recommend saving your password.

sprers.eu which under sprers.eu keep crashing and causes every window refreshing #

Not always can reproducing this problem.

WSL logs:

  • Attach WSLg logs from

I've checked these logs, the really interesting parts listed here:

sprers.eu:

sprers.eu

sprers.eu

and one more important thing here which from Windows Logs:

don't crash

Today I noticed my whole Windows keep refreshing everything per second, including almost every window, especially for the "Notification Area", which previously Windows 11 keeps buggy refreshing and flickering。

So, I'm trying to figure out which naughty process causes this and with which from , I've noticed this:

1

The rdp client process keeps crashing, and sprers.eu came out. This happens every second.

Tried shutting down WSL by , they calm down. but once WSL restarted, turns to that situation again.

but minutes after, it's fine and stable again, and during that time, I have not making any noticeable action.

Windows MSTSC RDP crashes shortly after launch

Discus and support MSTSC RDP crashes shortly after launch in Windows 10 BSOD Crashes and Debugging to solve the problem; Shortly after launching a remote app on a single computer other machines work just fine the program crashes. It shows that it is connected to the Discussion in 'Windows 10 BSOD Crashes and Debugging' started by slaytons, May 18,

Thema:

MSTSC RDP crashes shortly after launch

  1. MSTSC RDP crashes shortly after launch - Similar Threads - MSTSC RDP crashes

  2. System Crashes Shortly after startup

    in Windows 10 Gaming
    System Crashes Shortly after startup: SourceWindowsSummaryShut down unexpectedlyDate‎06/‎07/‎ StatusNot reportedProblem signatureProblem Event Name: BlueScreenCode: 10eParameter 1: 17Parameter 2: ffffdParameter 3: 0Parameter 4: ffffffffcb6OS version: 10_0_Service Pack: 0_0Product
  3. System Crashes Shortly after startup

    in Windows 10 Software and Apps
    System Crashes Shortly after startup: SourceWindowsSummaryShut down unexpectedlyDate‎06/‎07/‎ StatusNot reportedProblem signatureProblem Event Name: BlueScreenCode: 10eParameter 1: 17Parameter 2: ffffdParameter 3: 0Parameter 4: ffffffffcb6OS version: 10_0_Service Pack: 0_0Product
  4. Disable Windows Hello for RDP mstsc or change default setting

    in Windows 10 Gaming
    Disable Windows Hello for RDP mstsc or change default setting: Hi!,When I connect to servers with RDP I get windows hello PIN as default login method. Is there a way to disable windows hello for mstsc or change the default authentication method?Now I have to click more options all day long and use a different account
  5. Disable Windows Hello for RDP mstsc or change default setting

    in Windows 10 Software and Apps
    Disable Windows Hello for RDP mstsc or change default setting: Hi!,When I connect to servers with RDP I get windows hello PIN as default login method. Is there a way to disable windows hello for mstsc or change the default authentication method?Now I have to click more options all day long and use a different account
  6. Games crashing shortly after opening.

    in Windows 10 Gaming
    Games crashing shortly after opening.: Many of my games from steam crash after starting, I'm not sure what is causing this, as I have already made sure everything is updated. I also did a fresh install of windows, and that failed to fix it. Inside of my event viewer there seems to be a high number of
  7. Games crashing shortly after opening.

    in Windows 10 Software and Apps
    Games crashing shortly after opening.: Many of my games from steam crash after starting, I'm not sure what is causing this, as I have already made sure everything is updated. I also did a fresh install of windows, and that failed to fix it. Inside of my event viewer there seems to be a high number of
  8. Games crashing shortly after opening.

    in Windows 10 BSOD Crashes and Debugging
    Games crashing shortly after opening.: Many of my games from steam crash after starting, I'm not sure what is causing this, as I have already made sure everything is updated. I also did a fresh install of windows, and that failed to fix it. Inside of my event viewer there seems to be a high number of
  9. Windows 10 File Explorer Crashing shortly after launching

    in Windows 10 Network and Sharing
    Windows 10 File Explorer Crashing shortly after launching: Hello, My File Explorer crashes shortly after opening. I've tried all recommended troubleshooting approaches to no avail. Here is the diagnostic for my most recent crash. Source Windows Explorer Summary Stopped working Date ‎1/‎21/‎ PM Status
  10. How can I fix my MSTSC/RDP? Its not launching.

    in Windows 10 Network and Sharing
    How can I fix my MSTSC/RDP? Its not launching.: [ATTACH][ATTACH][ATTACH] How can I fix my mstsc/rdp? It doesn't seem to start, and the icons are not similar to the images I see on everyone else. I have enabled remote desktop connection, disabled firewall, and antivirus, and the RDP doesn't seem to start/launch. PS: the

Users found this page by searching for:

  1. Event ID Faulting application name: sprers.eu version:

Event ID — RemoteApp and Desktop Connection Configuration

Event ID — RemoteApp and Desktop Connection Configuration

Published: January 8,

Applies To: Windows Server R2

RemoteApp and Desktop Connection is configured by using the Control Panel.

Event Details

Product: Windows Operating System
ID:
Source: Microsoft-Windows-RemoteApp and Desktop Connections
Version:
Symbolic Name: TSWORKSPACE_SETUP_GENERIC_ERROR
Message: An error occurred. Contact your workplace administrator for sprers.eution name: %1Connection URL: %2Error code: %3, %4

Resolve
Identify and fix configuration issues with Remote Desktop Web Access

To resolve this issue, do the following things:

  • If you are using an RD Connection Broker server, you must ensure that the RD Connection Broker server is available on the network.
  • If you are using one or more RemoteApp sources, you should ensure that the RemoteApp source name is correct.

To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.

Ensure that the RD Connection Broker server is available on the network

The following are some troubleshooting steps that you can perform to help identify the root cause of the problem:

  • Ping other computers on the network to help determine the extent of the network connectivity issue.
  • If you can ping other servers but not the domain controller, try to ping the RemoteApp source server from another computer. If you cannot ping the RD Connection Broker server from any computer, first ensure that the RD Connection Broker server is running. If the RD Connection Broker server is running, check the network settings on the RD Connection Broker server.
  • Check the TCP/IP settings on the local computer by doing the following:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
    3. Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter.
    4. Type ping IP_address, where IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.
    5. Type ping DNS_server, where DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.
    6. If the RD Connection Broker server is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware.
  • In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type sprers.eu, and then click OK.
  • Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling.
  • Check firewall settings by using the Windows Firewall with Advanced Security snap-in.
  • Check IPsec settings by using the IP Security Policy Management snap-in.

Ensure that the RemoteApp source name is correct

You can ensure that the RemoteApp source name is correct by using Remote Desktop Web Access Configuration.

To ensure that the RemoteApp source name is correct:

  1. On the RD Web Access server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Configuration.
  2. Enter the appropriate user name and password.
  3. Click Configuration.
  4. In the Source name box, ensure that the RemoteApp source name represents a NETBIOS name or fully qualified domain name of the RemoteApp source. If you are using more than one RemoteApp source, ensure that each source name is separated with a semicolon.

Verify

To verify that RemoteApp and Desktop Connection is configured correctly, you should start a RemoteApp program that is published by using RemoteApp and Desktop Connection.

To start a RemoteApp program that is published by using RemoteApp and Desktop Connection:

  1. On a client computer, click Start, point to All Programs, point to RemoteApp and Desktop Connections, point to Enterprise Remote Access, and then click a RemoteApp program.
  2. Verify that the RemoteApp program opens successfully.

Related Management Information

RemoteApp and Desktop Connection Configuration

Remote Desktop Services

Related:

Read these next

Any ideas oh how I can fix this? 

Windows 10 Home Version - all updates installed, anti-virus removed and Windows Firewall turned off. 

Log Name:     Application
Source:       Application Error
Date:         11/6/ AM
Event ID:    
Task Category: ()
Level:       Error
Keywords:     Classic
User:         N/A
Computer:     Sandra-PC
Description:
Faulting application name: sprers.eu, version: , time stamp: 0x18cef
Faulting module name: sprers.eu, version: , time stamp: 0x99ca
Exception code: 0xc
Fault offset: 0xa6
Faulting process id: 0x
Faulting application start time: 0x01db67ecd3
Faulting application path: C:\WINDOWS\system32\sprers.eu
Faulting module path: C:\WINDOWS\SYSTEM32\sprers.eu
Report Id: 09fde3af-4dbaebbd5c90b70
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="sprers.eu">;
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0"></EventID>
    <Level>2</Level>
    <Task></Task>
    <Keywords>0x</Keywords>
    <TimeCreated SystemTime="TZ" />
    <EventRecordID></EventRecordID>
    <Channel>Application</Channel>
    <Computer>Sandra-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>sprers.eu</Data>
    <Data></Data>
    <Data>18cef</Data>
    <Data>sprers.eu</Data>
    <Data></Data>
    <Data>99ca</Data>
    <Data>c</Data>
    <Data>a6</Data>
    <Data></Data>
    <Data>01db67ecd3</Data>
    <Data>C:\WINDOWS\system32\sprers.eu</Data>
    <Data>C:\WINDOWS\SYSTEM32\sprers.eu</Data>
    <Data>09fde3af-4dbaebbd5c90b70</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

checkBest Answer

  • What have you tried to resolve this issue?
    Have you tried "sfc /scannow"?
    Try DISM if that didn't help:
    DISM /Online /Cleanup-Image /RestoreHealth
    Also, If you have unnecessary program that has been installed on the machine try to uninstall it.

  • View Best Answer in replies below
    • What have you tried to resolve this issue?
      Have you tried "sfc /scannow"?
      Try DISM if that didn't help:
      DISM /Online /Cleanup-Image /RestoreHealth
      Also, If you have unnecessary program that has been installed on the machine try to uninstall it.

    • Hi, yes, ran both sfc and dism.  Also have uninstalled anti-virus and turned off Windows Firewall.  Still crashing when trying to connect to remote desktop using RDP. 

      Looks like to me a problem with the sprers.eu but I don't know how to fix this. 

    • The remote is a server farm.  Others have no issues RDPing into the server farm. The only difference is that this is a desktop running Windows 10 Home (a home PC) instead of Windows 10 Professional, but I don't know why this would make a difference. 

    • Yes, all local devices and resources have been unchecked in the RDP settings. Still crashes. 

    • Have you tried disabling UAC on both sides?

    • Just tried to disable UAC and still crashing. 

    • Try with another user account.

    • Try to reboot the machine, too.

    • There was an OEM application called HP Simple Pass (password management) that I removed and now it works.  Thanks very much for your help. 

      8 found this helpfulthumb_upthumb_down
    • Big Green Man
      Big Green ManThis person is a Verified Professional

      Verify your account to enable IT peers to see that you are a professional.

      mace

      Windows 10 Expert

      • check Best Answers
      • thumb_up Helpful Votes
      • format_list_bulleted 1 How-to

      beowulf wrote:

      There was an OEM application called HP Simple Pass (password management) that I removed and now it works.  Thanks very much for your help. 

      I recommend marking this as best answer instead of the one you have marked. You won't get any points for it, but it will make it easier for someone in the future to find a solution.

      3 found this helpfulthumb_upthumb_down
    • If I can offer a suggestion, MS have a Remote Desktop Connection Manager that allows you to save a list of remote hosts and connect to multiple simultaneously. It's worth a look if you do a bit of RDP.

    • beowulf wrote:

      There was an OEM application called HP Simple Pass (password management) that I removed and now it works.  Thanks very much for your help. 

      Thanks for posting this.

      Just had a user with a BYOD trying to connect through to our RDS farm. Our helpdesk tech was struggling with mstsc crashing. I Google'd it and first hit on search results was this thread.

      Asked him: "It isn't a HP laptop by any chance is it?"
      Answer: "Yea, it is"
      Me:"Has it got HP Simple Pass installed?"

      Uninstalled that & hey presto!

      Me made look super awesome :-D

      5 found this helpfulthumb_upthumb_down
    • Hi! Just want to add my two cents.

      I had one user who would get disconnected from a RDP session like seconds after RDPing into a certain terminalserver. This only happened against this TS, I tried RDPing into other servers in my networks and everything was fine - no disconnect after some seconds. This pattern was consistent with any account that I used on the pc to troubleshoot. Turns out it was a disconnected HP laserjet printer which was triggering this crash and event, after I removed that printer from the pc- RDPing to the TS was fine, no disconnect after login anymore.

      TLDR: make sure there are no printers which are crashing the RDP session.

    • RobClarke 

      THANK YOU for this, just spent a couple of hours on someones personal laptop trying to fix this problem, found this post and, tada! Worked immediately upon removal.

      THANK YOU AGAIN.

    • NICE!!! Killing Simplepass FTW!

    • Thanks! This worked.

      beowulf wrote:

      Any ideas oh how I can fix this? 

      Windows 10 Home Version - all updates installed, anti-virus removed and Windows Firewall turned off. 

      Log Name:     Application
      Source:       Application Error
      Date:         11/6/ AM
      Event ID:    
      Task Category: ()
      Level:       Error
      Keywords:     Classic
      User:         N/A
      Computer:     Sandra-PC
      Description:
      Faulting application name: sprers.eu, version: , time stamp: 0x18cef
      Faulting module name: sprers.eu, version: , time stamp: 0x99ca
      Exception code: 0xc
      Fault offset: 0xa6
      Faulting process id: 0x
      Faulting application start time: 0x01db67ecd3
      Faulting application path: C:\WINDOWS\system32\sprers.eu
      Faulting module path: C:\WINDOWS\SYSTEM32\sprers.eu
      Report Id: 09fde3af-4dbaebbd5c90b70
      Faulting package full name:
      Faulting package-relative application ID:
      Event Xml:
      <Event xmlns="sprers.eu">;
        <System>
          <Provider Name="Application Error" />
          <EventID Qualifiers="0"></EventID>
          <Level>2</Level>
          <Task></Task>
          <Keywords>0x</Keywords>
          <TimeCreated SystemTime="TZ" />
          <EventRecordID></EventRecordID>
          <Channel>Application</Channel>
          <Computer>Sandra-PC</Computer>
          <Security />
        </System>
        <EventData>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>18cef</Data>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>99ca</Data>
          <Data>c</Data>
          <Data>a6</Data>
          <Data></Data>
          <Data>01db67ecd3</Data>
          <Data>C:\WINDOWS\system32\sprers.eu</Data>
          <Data>C:\WINDOWS\SYSTEM32\sprers.eu</Data>
          <Data>09fde3af-4dbaebbd5c90b70</Data>
          <Data>
          </Data>
          <Data>
          </Data>
        </EventData>
      </Event>

      beowulf wrote:

      Any ideas oh how I can fix this? 

      Windows 10 Home Version - all updates installed, anti-virus removed and Windows Firewall turned off. 

      Log Name:     Application
      Source:       Application Error
      Date:         11/6/ AM
      Event ID:    
      Task Category: ()
      Level:       Error
      Keywords:     Classic
      User:         N/A
      Computer:     Sandra-PC
      Description:
      Faulting application name: sprers.eu, version: , time stamp: 0x18cef
      Faulting module name: sprers.eu, version: , time stamp: 0x99ca
      Exception code: 0xc
      Fault offset: 0xa6
      Faulting process id: 0x
      Faulting application start time: 0x01db67ecd3
      Faulting application path: C:\WINDOWS\system32\sprers.eu
      Faulting module path: C:\WINDOWS\SYSTEM32\sprers.eu
      Report Id: 09fde3af-4dbaebbd5c90b70
      Faulting package full name:
      Faulting package-relative application ID:
      Event Xml:
      <Event xmlns="sprers.eu">;
        <System>
          <Provider Name="Application Error" />
          <EventID Qualifiers="0"></EventID>
          <Level>2</Level>
          <Task></Task>
          <Keywords>0x</Keywords>
          <TimeCreated SystemTime="TZ" />
          <EventRecordID></EventRecordID>
          <Channel>Application</Channel>
          <Computer>Sandra-PC</Computer>
          <Security />
        </System>
        <EventData>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>18cef</Data>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>99ca</Data>
          <Data>c</Data>
          <Data>a6</Data>
          <Data></Data>
          <Data>01db67ecd3</Data>
          <Data>C:\WINDOWS\system32\sprers.eu</Data>
          <Data>C:\WINDOWS\SYSTEM32\sprers.eu</Data>
          <Data>09fde3af-4dbaebbd5c90b70</Data>
          <Data>
          </Data>
          <Data>
          </Data>
        </EventData>
      </Event>

      beowulf wrote:

      Any ideas oh how I can fix this? 

      Windows 10 Home Version - all updates installed, anti-virus removed and Windows Firewall turned off. 

      Log Name:     Application
      Source:       Application Error
      Date:         11/6/ AM
      Event ID:    
      Task Category: ()
      Level:       Error
      Keywords:     Classic
      User:         N/A
      Computer:     Sandra-PC
      Description:
      Faulting application name: sprers.eu, version: , time stamp: 0x18cef
      Faulting module name: sprers.eu, version: , time stamp: 0x99ca
      Exception code: 0xc
      Fault offset: 0xa6
      Faulting process id: 0x
      Faulting application start time: 0x01db67ecd3
      Faulting application path: C:\WINDOWS\system32\sprers.eu
      Faulting module path: C:\WINDOWS\SYSTEM32\sprers.eu
      Report Id: 09fde3af-4dbaebbd5c90b70
      Faulting package full name:
      Faulting package-relative application ID:
      Event Xml:
      <Event xmlns="sprers.eu">;
        <System>
          <Provider Name="Application Error" />
          <EventID Qualifiers="0"></EventID>
          <Level>2</Level>
          <Task></Task>
          <Keywords>0x</Keywords>
          <TimeCreated SystemTime="TZ" />
          <EventRecordID></EventRecordID>
          <Channel>Application</Channel>
          <Computer>Sandra-PC</Computer>
          <Security />
        </System>
        <EventData>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>18cef</Data>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>99ca</Data>
          <Data>c</Data>
          <Data>a6</Data>
          <Data></Data>
          <Data>01db67ecd3</Data>
          <Data>C:\WINDOWS\system32\sprers.eu</Data>
          <Data>C:\WINDOWS\SYSTEM32\sprers.eu</Data>
          <Data>09fde3af-4dbaebbd5c90b70</Data>
          <Data>
          </Data>
          <Data>
          </Data>
        </EventData>
      </Event>

      beowulf wrote:

      Any ideas oh how I can fix this? 

      Windows 10 Home Version - all updates installed, anti-virus removed and Windows Firewall turned off. 

      Log Name:     Application
      Source:       Application Error
      Date:         11/6/ AM
      Event ID:    
      Task Category: ()
      Level:       Error
      Keywords:     Classic
      User:         N/A
      Computer:     Sandra-PC
      Description:
      Faulting application name: sprers.eu, version: , time stamp: 0x18cef
      Faulting module name: sprers.eu, version: , time stamp: 0x99ca
      Exception code: 0xc
      Fault offset: 0xa6
      Faulting process id: 0x
      Faulting application start time: 0x01db67ecd3
      Faulting application path: C:\WINDOWS\system32\sprers.eu
      Faulting module path: C:\WINDOWS\SYSTEM32\sprers.eu
      Report Id: 09fde3af-4dbaebbd5c90b70
      Faulting package full name:
      Faulting package-relative application ID:
      Event Xml:
      <Event xmlns="sprers.eu">;
        <System>
          <Provider Name="Application Error" />
          <EventID Qualifiers="0"></EventID>
          <Level>2</Level>
          <Task></Task>
          <Keywords>0x</Keywords>
          <TimeCreated SystemTime="TZ" />
          <EventRecordID></EventRecordID>
          <Channel>Application</Channel>
          <Computer>Sandra-PC</Computer>
          <Security />
        </System>
        <EventData>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>18cef</Data>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>99ca</Data>
          <Data>c</Data>
          <Data>a6</Data>
          <Data></Data>
          <Data>01db67ecd3</Data>
          <Data>C:\WINDOWS\system32\sprers.eu</Data>
          <Data>C:\WINDOWS\SYSTEM32\sprers.eu</Data>
          <Data>09fde3af-4dbaebbd5c90b70</Data>
          <Data>
          </Data>
          <Data>
          </Data>
        </EventData>
      </Event>

      beowulf wrote:

      Any ideas oh how I can fix this? 

      Windows 10 Home Version - all updates installed, anti-virus removed and Windows Firewall turned off. 

      Log Name:     Application
      Source:       Application Error
      Date:         11/6/ AM
      Event ID:    
      Task Category: ()
      Level:       Error
      Keywords:     Classic
      User:         N/A
      Computer:     Sandra-PC
      Description:
      Faulting application name: sprers.eu, version: , time stamp: 0x18cef
      Faulting module name: sprers.eu, version: , time stamp: 0x99ca
      Exception code: 0xc
      Fault offset: 0xa6
      Faulting process id: 0x
      Faulting application start time: 0x01db67ecd3
      Faulting application path: C:\WINDOWS\system32\sprers.eu
      Faulting module path: C:\WINDOWS\SYSTEM32\sprers.eu
      Report Id: 09fde3af-4dbaebbd5c90b70
      Faulting package full name:
      Faulting package-relative application ID:
      Event Xml:
      <Event xmlns="sprers.eu">;
        <System>
          <Provider Name="Application Error" />
          <EventID Qualifiers="0"></EventID>
          <Level>2</Level>
          <Task></Task>
          <Keywords>0x</Keywords>
          <TimeCreated SystemTime="TZ" />
          <EventRecordID></EventRecordID>
          <Channel>Application</Channel>
          <Computer>Sandra-PC</Computer>
          <Security />
        </System>
        <EventData>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>18cef</Data>
          <Data>sprers.eu</Data>
          <Data></Data>
          <Data>99ca</Data>
          <Data>c</Data>
          <Data>a6</Data>
          <Data></Data>
          <Data>01db67ecd3</Data>
          <Data>C:\WINDOWS\system32\sprers.eu</Data>
          <Data>C:\WINDOWS\SYSTEM32\sprers.eu</Data>
          <Data>09fde3af-4dbaebbd5c90b70</Data>
          <Data>
          </Data>
          <Data>
          </Data>
        </EventData>
      </Event>

      I Found that in my 'Control Panel>Devices>Printers" I had Toshiba Printer driver. 

      I Removed it completely from the list of printers and also from "Print Server Properties>Driver"

    • Just came to say this fixed a problem one of our remote desktop users was having.

      As as soon as I uninstalled HP SimplePass the RDS connection worked fine.

      Thanks a lot!

    • Also, if you're not doing printing from RDP, at the Remote Desktop screen, click on Show Options, Local Resources tab, and uncheck Printers

    • What are your thoughts on the concept of "quiet quitting"?

      What are your thoughts on the concept of "quiet quitting"?

      IT & Tech Careers

      Whether you were surfing social media, listening to a podcast/news, or just chatting with friends, you have probably heard of the term/concept of "quiet quitting". I know this isn't a new term/concept but it has seen a recent surge in discussion especiall

    • How Old is too Old (Servers, not staff;-)

      How Old is too Old (Servers, not staff;-)

      Hardware

      kind of a re-hash of an old question (), I'm currently removing old kit from our racks & given some of it is now rapidly heading for 13 years + old & has only just been removed from service (Poweredge anybody?) I was wondering what the consensus

    • Snap! Chrome clipboard bug, private cellular, Win11 Start, IT Pro AI art, & more

      Snap! Chrome clipboard bug, private cellular, Win11 Start, IT Pro AI art, & more

      Spiceworks Originals

      Your daily dose of tech news, in brief. Welcome to September ! In some ways, it feels like it's taken forever to get here; in other ways, time is flying by way too quickly. You need to hear this. Google Chrome bug lets sites write to clip

    • Invalid operation for device '0'

      Invalid operation for device '0'

      Virtualization

      Good day fellow Spiceheads,I am struggling with a simple task, a disk expansion on a sprers.eu C drive expands no problem, but the D drive gives me the error as per the headline.I logged a call with VMWare and was advised to disable replication and then try

    • Best practice for SSL certificate for server in DMZ?

      Best practice for SSL certificate for server in DMZ?

      Security

      I have an application server in our DMZ that will be using: sprers.eut would be the best route to provide a SSL certificate for it?  Our company website (sprers.eu) is hosted by a third party and has an SSL certificate sprers.eu

    David Vielmetter

    [the problem]

    Establishing an Remote Desktop Connection via Remote Desktop Protocol (RDP) to another system using Windows 10 build causes the session to crash shortly after being created. The error given is generic. The event log shows that the faulting application name sprers.eu version crashed with an exception code of 0x and because of module sprers.eu version

    Error: Remote Desktop Connection has stopped working

    [the solution]

    The issue is caused by a printer driver where when the affected printers are redirected as part of the RDP session, the session crashes unexpectedly.

    1. The long term fix should be to apply all missing updates and upgrade to the latest build.
    2. The short fix is to stop redirecting printers as part of the RDP connection profile.

    That&#;s it.

    Tricks

    faulting app sprers.eu, faulting module, sprers.eu crashes, sprers.eu version , rdp, Remote Desktop Connection, windows 10 sprers.eu, windows 10 rdc crashes, windows 10 rdp crashes, windows 10 remote desktop connection crashing


    application error 1000 mstsc

    0 Comments

    Leave a Comment