The application cannot be run ошибка

Issue

AVTECH CCTV system remote access fails with following Java errors:

Application Blocked for Security.
Certificate has been revoked.
The application will not be executed.

Application Blocked. Click for details.
Application Blocked for Security. The application cannot be run.
Reason: The certificate used to identify this application has been revoked.

Resolution

• Go to Control Panel and open Java Control Panel.
• In Advanced tab scroll down to «Perform signed code certificate revocation checks on» and change it to «Do not check (not recommended)«

Note: This should only be used as a temporary workaround to run trusted application. disabling certificate revocation check is a security risk!

June 2016
AVTECH DVR
Windows 10
Internet Explorer 11
Java 8

Reading time
6 min

Views 3.2K

Read this article to learn how to fix the problem with running an application on PC, and we will find out why this error appears and how to solve the problem.

The core of the problem

On the Internet, there are lots of websites offering to install various applications and programs. At an early stage, Windows 10 operating system can detect and warn the user of possible issues, or even block a harmful application or program at once.

For this purpose, Microsoft has improved greatly the built-in defense component, SmartScreen. Its main task is to protect the user from apps provided by questionable developers. SmartScreen helps to reveal any previously detected malware, applications or websites created for malicious purposes, and takes informed decisions on blocking their access, download or use on your personal computer or another computing device.

At the first stage, SmartScreen analyzes all applications, programs and webpages for any suspicious activities. The next step will be to compare suspicious apps and webpages with the list of programs and websites recognized to be harmful. In case of a coincidence, SmartScreen will block download or installation for such a program, and display a corresponding notification for the user.

Obviously, SmartScreen is quite a useful feature in Windows 10 and using it seems absolutely justified. However, frequent error messages or warning notifications displayed while you are working with an application or website that you trust can become quite irritating. In that case, SmartScreen is easy to disable – if you know the app we are talking about is absolutely safe.

This security feature can display quite a number of various warnings and error messages, but most of these can be sorted out on your own. Mostly, these are issues related to providing additional permissions or signing in to an account with administrator’s rights.

Still, cases when you see a SmartScreen message saying This app can’t run on your PC are totally different. Such messages only suggest that you contact the program’s developer for advice – and that’s all. Also, you can face such messages when apps that used to run seamlessly on your computer, suddenly can’t start, for no evident reason. Yet don’t worry: even if you see the error This app can’t run on your PC in Windows 10, here’s what you can do.

The error This app can’t run on your PC

If you see such a message, it means there is a compatibility error. The application you are trying to install is incompatible with your operating system, Windows 10. You may also encounter this error if the application requires special permissions to run – and the current user account lacks them. This error only appears when you are trying to install an application, and never does when you start one. If an application is already installed to your computer, starting it will never trigger this error. There are two ways to fix it.

Use your account with administrator rights

When you see this error message, it might be due to your signing in to an account which doesn’t have administrator rights. To exclude this one out, check the account you are using now. If the current account is not the administrator’s one, switch to that account, and try installing the application again. If this method doesn’t work, try another one on the list.

32-bit or 64-bit application

If you’re using the 32-bit version of Windows 10 and trying to run a 64-bit version of the program, the error should have been expected. Similarly, if you’re trying to install a 32-bit program onto a 64-bit version of Windows 10, this error may also take place. If the problem comes from bitness, there’s only one solution – you’ve got to find the proper version of the necessary application and install it.

Disable SmartScreen in Windows 10

Sometimes, the error This app can’t run on your PC may be false. That’s why if the advice I have given you in this article didn’t help you and you still face this error, and you still need to run this app despite the warning, try disabling SmartScreen filter. In this tutorial, we will show you three ways to disable the security feature, as it is applied to the entire Windows 10 operating system, to applications received from Microsoft Store, and to the system’s featured browser, Microsoft Edge.

Disable SmartScreen in Windows 10 with Windows Defender Security Center

In this case, you should open Windows Defender Security Center. It can be done in a few ways.

Click on the Start button on the Taskbar, and open the main Windows menu, then click the gearwheel symbol. Alternatively, drag the scroll bar down until you find the line Settings.

In the application window, drag the slider down and select the section Update and Security.

On the left, select Windows Security, and on the right click on Open Windows Defender Security Center.

It opens the main window of Windows Defender Security Center.

In the side menu on the right, select App & browser control. You will be redirected to the page where you can configure SmartScreen for applications and browsers.

Here, you can disable Check apps & files, SmartScreen for Microsoft Edge and SmartScreen for Microsoft Store apps. Check the Off option in corresponding sections.

When the pop-up notification from Windows User Account Control asks Do you want to allow this app to make changes to your device? click Yes for the changes to take effect.

Disable SmartScreen in Windows 10 with the Registry Editor

Note: It is important to remember that anything you do to the registry is on your own responsibility. Any actions involving the registry may cause irreversible consequences. Windows 10 may begin working with errors, some apps or programs may not be able to start, the operating system can crash or have problems when booting. Before you start modifying the registry, we strongly recommend backing it up, just in case. To do it, open the Registry Editor, choose the File tab in the main menu, and select Export. The operating system will suggest you to give a name to the registry backup and select the directory where to save it. Choose a name that will help you to remember when exactly this backup was created. The best name would be the date of creation, for example, 02-04-2019. After that, click Save. Now you will have a registry backup file which you can use to restore it if necessary.

One more time, open the Run dialogue box in any of the ways described in this article (for example, by pressing the keyboard shortcut Windows + R for quick access to the Runwindow). In the command prompt field, type the command for opening the Registry Editor (regedit) and click ОК to perform the command.

When the pop-up notification from Windows User Account Control asks Do you want to allow this app to make changes to your device? click Yes and open the Registry Editor window.

In the left-side part of the window, follow the path:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsSystem

You can also use a different method for accessing this particular section of the registry. Just copy and paste it into the address bar of the Registry Editor (it’s under the main menu). This way, you can avoid possible errors when selecting the registry section, as the left panel displays many similar directories, and this specific method helps you make sure you use the correct address.

Right-click on an empty area on the right, select New from the context menu that appears, and click on the nested menu option DWORD value (32 bit).

Give the new DWORD value the name EnableSmartScreen. Double-click on it, or right-click on it and select Modify from the menu.

In the window Edit DWORD value (32 bit) set the Value data to0 (this value data will be used by default). Click ОК or press Enter on your keyboard to save the changes to the value.

Now close the Registry Editor window and restart your computer. After that, SmartScreen will be disabled.

Disable SmartScreen in Windows 10 with the Local Group Policy Editor

If your computer is running Windows 10 Home Edition, you won’t be able to use the functionality of the Local Group Policy Editor, as this utility is not excluded into this particular version of the operating system. For other versions of Windows 10, do the following.

Open the Run dialogue box in any of the ways described in today’s article (for example, right-click on the Start button in the Taskbar, and select the Run dialogue box in the menu that opens). In the Command Prompt window, type the command gpedit.msc.

Click ОК or press Enter on your keyboard to confirm your action, and the Local Group Policy Editor window will appear.

In the left-side panel, follow this path:

Computer Configuration – Administrative Templates – Windows Components – Windows Defender SmartScreen.

There are two subsections, Explorer and Microsoft Edge. Each of them contains a policy setting Configure Windows SmartScreen that allows you to enable or disable the filter as you like. Double-click on it, or right-click on it and select Edit from the menu.

In the window that opens, check the option for Disabled, then click Apply and ОК to save the changes you have made.

Apply this algorithm to every subsection: Explorer and Microsoft Edge. In the first subsection, it disables checking files in Windows 10, and in the second subsection it turns off SmartScreen in Microsoft Edge. After saving the changes, close the Local Group Policy Editor, and the SmartScreen feature will be disabled.

There is also a way to disable SmartScreen in Microsoft Edge in the browser settings. Open Microsoft Edge and click on the three-dot button in the top right corner to open the main menu.

Select Settings.

Then click View advanced settings.

Scroll down to find the line Help protect me from malicious sites and downloads with Windows Defender SmartScreen and set the slider to Off.

Finally, when the SmartScreen feature is disabled, make sure that your application starts and works correctly now. If you see the error again, the problem must be in the application itself, not in the security feature.

Then all you can do is to wait for another update to fix this issue, or find another program to replace the faulty app. If you disabled the SmartScreen feature, make sure you turn it on again after the necessary application is installed. It’s not a good idea to leave your system open to threats and without protection, so turn the feature on again and improve the security of your operating system.

See the full article with all additional video tutorials. If you still have any questions, please ask in a comments. Also visit our Youtube channel, there are over 400 video tutorials.

11 Ways To Fix This App Can’t Run on Your PC Windows 10 – One of the error messages that often appear when the application can’t be opened in Windows 10, ” This app can’t run on your PC, to find a version for your PC check with the publisher software “. This kind of problem is quite common and experienced by many people, especially when running applications that are not from Microsoft.

The main cause of this problem is compatibility issues between the application and the version of Windows that the system considers incompatible. It could also be because the application or game that is going to run is filtered by Windows so the process is blocked.

Read more:

• How to Reduce Brightness in Windows 7/8/10
• 4 Ways to find your Computer’s System Specification
• How To Update Windows 10 Offline Permanently
• How to Restore Windows Photo Viewer Windows 10

Windows 10 has a feature to block unknown applications from unverified developers, this feature will be active by default in order to prevent the entry of applications that contain malware and viruses.

Other causes could also be due to corrupted application files, corrupt system files, or problems caused by malware and viruses. On this occasion, I will try to provide several solutions that you can try to solve.

How to Fix This App Can’t Run on Your PC Windows 10 PC Laptop

To properly follow this guide: How to fix this app can’t run on your PC windows.

1. Enter the Settings Menu

The first step is to enter the Settings menu by clicking on the Start button> then clicking the Settings button (gear icon).

2. Select the Accounts menu

In the Settings window find and click on the Accounts menu.

3. Select the Family & other users tab

On the left panel, click on the Family & other users tab.

4. Click Add someone else to this PC

Pull down a little bit until you find the Other users> section then click on the Add someone else to this PC button.

5. Select I don’t have this person’s sign-in information

A window for adding a Microsoft account will open, at the bottom of the column there is an option I don’t have this person’s sign-in information> click on this option.

6. Click on the option Add a user without a Microsoft account

Since we are going to create a local account, there is no need to create a new Microsoft account. Therefore, what you need to do next is click again on the option Add a user without a Microsoft account.

7. Fill in the name and password for the new account

A window for creating a new Administrator account will open, fill in the name and password of the account as desired. When finished click on the Next button> follow the process to completion.

8. Click on Change account type in the new account

Back to the home page of Accounts settings> in the Other user section you will see the account you just created. Click on the Change account type button below it.

9. Select Administrator

Click on the Administrator option to change the local account that was just created to the administrator.

10. Login with the new Administrator account

The last step is to log out of your current account by clicking on the Start button> clicking on the icon/account photo> selecting Sign out> and then logging in with the new Administrator account.

After logging back into Windows using the new Administrator account, try running the problematic application again. Can it be done?

If it doesn’t work, then please try some of the other alternative solutions below.

Use an application compatible with Windows architecture (32bit or 64bit)

As mentioned earlier, applications that cannot be opened with the error This app can’t run on your PC are generally caused by compatibility issues. When you try to run an application with 64-bit architecture for Windows with 32-bit architecture, an error like this will of course occur.

64-bit applications can only run on 64-bit operating systems as well. If you are using the Windows version with a 32-bit architecture then you must use an application with a 32-bit architecture as well.

To check whether Windows on your laptop is 32bit or 64bit you can click on the Start button> select Settings> About> pay attention to the System type description. There you will see whether Windows you are using 32bit or 64bit.

#1. Try using an older or newer version of the app

Compatibility problems can also occur when the application is upgraded (update/upgrade). A bug in the program code might cause it not to work properly as before.

If This app can’t run on your PC error occurs after you update the application, you may suspect that the latest version of the application has a bug. Try reinstalling an older version of the app and see if this error still appears or not.

You can experiment with yourself by trying an older or newer version of the program. There may be a working version of the program.

#2. Run as administrator

Some programs require administrator privileges in order to run. If your application cannot be opened by double-clicking, try using the right-click method on the application> then select Run as administrator.

In this way, the application will run with administrator access permissions. You can also set the application to run as an administrator each time you open it. The trick is to right-click on the application shortcut> select Properties> click on the Shortcut tab> click the Advanced button> check the Run as Administrator option> OK.

#3. Run the program in Compatibility mode

Some programs are specifically designed to run on certain versions of Windows only. For example, there are programs specifically made for Windows 7, Windows Vista, Windows 8, or even Windows XP.

When trying to run it on Windows 10, compatibility issues can arise. This will prevent the application from being opened. The solution is to try to run the application in compatibility mode according to the Windows version.

First, find the location of the executable (.exe) file from the program, right-click on the application shortcut> select Open file location.

After the .exe file is found, right-click on the file> then select Properties.

In the Properties window click on the Compatibility tab> in the Compatibility mode section, check the Run this program in compatibility mode for> option then select the appropriate Windows version> click Apply> OK.

Now the application is set to run in compatibility mode according to the required version of Windows. Try opening the app and see if this method works.

#4. Run the file system checker

In Windows 10, there is a feature called System File Checker (SFC). This feature is used to scan system files and repair them automatically if any damage is found.

Applications that cannot be opened with the This app can’t run on your PC error message may appear due to corrupted system files, so running SFC is a step worth trying.

First, open the Command Prompt with administrator access, how to click on the Start button> type cmd> the recommended Command Prompt program will appear> click on Run as an administrator in the right panel.

At the Command Prompt type the following command:

sfc / scannow

Then press enter.

Wait for the process to finish.

If any damage is found in the system files, SFC will try to repair them automatically, you can see the description on the screen. There’s nothing you need to do, just wait for the process to complete.

#5. Enable the Developer mode (side-loading) feature

If the application you are trying to install is not from the Windows Store then the side-loading feature must be activated. Try to check whether this feature is active in your Windows or not.

The trick is to click the Start button> click the Settings button> select the Update & Security menu> select the For developers menu> check the Developer mode option> Yes

#6. Turn off the smart screen feature

A SmartScreen is a built-in security feature in Windows 10 that functions as a filter against programs that are considered dangerous and contain malware.

When this feature is active, the possibility of false positives (wrong detection) can be experienced, especially in applications that come from developers who have not been verified by Microsoft.

When you experience this error that the app can’t run on your PC, turning off the Smartscreen is one step worth trying.

The trick is to click on the Start button> select Settings> select Update & Security> click on the Windows Security tab> then click the open Windows Security button.

After the Windows Security window opens select the App & browser control menu> click on the Reputation-based protection option> turn off all available features.

#7. Clear cache and temporary files

By cleaning junk files in Windows 10 you can also try to solve this problem. Stacking and overlapping cache files and temporary files might cause the application to not run properly. Cleaning it is the best solution that can be done.

You can use one of the best PC cleaner applications to make your work easier. The application will clean all existing junk files automatically.

#8. Full scan the computer with Windows Security / another antivirus

Viruses and malware can also cause damage to an application so that it can’t be opened, including causing the error This app can’t run on your PC. To ensure that your laptop is clean from viruses you can do a thorough scan using an antivirus.

You can use the default antivirus Windows 10, namely Windows Security or one of the best antivirus recommendations we have given in a previous post.

I myself prefer to use Windows Security because it is lighter and powerful enough to keep the computer free of viruses without being bothered by the offers or advertisements that usually exist in third-party antivirus applications.

To perform a full scan using Windows Security, follow the steps below.

First, go to the Settings menu > select Update & Security> select Windows Security> click on the Open Windows Security button.

After the Windows Security window opens, select the Virus & threat protection menu.

Click on the Scan options menu> check the Full scan option> click the Scan now button.

Wait until the scan is complete. If viruses and malware are detected, Windows Security will clean them automatically.

Making sure your laptop is clean of viruses is one very effective way to speed up Windows 10, so make sure you always do it regularly.

#9. Turn off VPN and Proxy (if any)

If your laptop or PC is connected to the internet via VPN and Proxy then you can turn it off first. Each application has a different policy regarding which countries can run the application. It could be that a country is blocked for some reason.

Another reason is security issues. When you use an application with different IP addresses from different countries, this can be considered suspicious and will cause your account to be blocked.

Certain VPN and Proxy settings can also cause connection failures to Microsoft servers, which can prevent Microsoft applications from running, especially those that require an internet connection.

#10. Windows Update

Updating is one effective step to keep Windows in the best condition. Updates not only contain feature updates, but also virus database updates, bug fixes, and updates for Microsoft applications. For original Windows 10 users, it’s a loss if you don’t update regularly.

When you experience an error either on the system or in the application, then updating might be one of the solutions that you can try. How to update Windows 10 is very easy.

First, click on the Start button> select Settings> select the Update & Security menu> select Windows Update> click the Check for updates button> wait for the process to finish.

#11. Reset the PC

This is the final solution if all the methods above have been tried and nothing works. You need to consider this carefully before doing a PC reset because existing applications will be deleted and Windows will return to a state of reinstallation.

After resetting the PC, try installing and running the problematic application, and see if this last solution works.

You also need to reinstall the required applications one by one. It’s even better if before the reset you have listed what applications should be installed to make the process easier.

Read more:

• How to Resolve Error Code 0x0003
• 7 Easy Ways to Enable WiFi on Laptop Windows
• How to Install and Use Apple Notes on Windows 10

Conclusion:

These are some of the solutions how to fix this app that can’t run on your PC Windows, you can solve the problem of applications that cannot be opened on Windows 10 with the error message This app can’t run on your PC.

I was trying to register a digital signature certificate on www.incometaxindiaefiling.gov.in.
When the site requested to run Java applet JRE7, which I allowed.
But then the small window pops up with the following message;

Application Blocked for security reason
The Application cannot be run.
Name: StoreCertificate
Location: http://incometaxindiaefiling.gov.in
Reason: Your security settings have blocked a self-signed application from running

                [  OK  ]       [   More Information...   ]

I was trying to register a digital signature certificate on www.incometaxindiaefiling.gov.in.
When the site requested to run Java applet JRE7, which I allowed.
But then the small window pops up with the following message;

Application Blocked for security reason
The Application cannot be run.
Name: StoreCertificate
Location: http://incometaxindiaefiling.gov.in
Reason: Your security settings have blocked a self-signed application from running
[ OK ] [ More Information… ]

Chosen solution

All Replies (3)

Dear Philipp
I’m really thankful fro your prompt response and for identifying the root problem.
I followed the instruction given on the link provided by you, but, the problem still continues.
It would be very helpful if you could suggest the way out with screenshots for a lay man like myself.

Symptoms

Consider the following scenario:

• You run a Windows Embedded Compact 7-based image on a touch screen device.

• You use Remote Desktop Protocol (RDP) to connect the device to a remote computer.

• You double-tap the icon of an application on the remote computer in the RDP session.

In this scenario, the application does not start.

Cause

This issue occurs because consecutive taps are not recognized as double-taps or double-clicks by the remote computer. Specifically, the tap coordinates that are sent from the Windows Embedded Compact 7-based RDP client are not close enough to qualify as double-taps or double-clicks.

Note This issue occurs almost exclusively on touch screen devices on which the precision of touch is less accurate.

Resolution

To resolve this issue, apply the following update. 

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in Windows
By default, this update is disabled after you apply it. To enable the update, set the DWORD value of the EnableDoubleClickDetect registry entry to 1. By default, the EnableDoubleClickDetect DWORD value does not exist, and you must create it in the following registry subkey:

HKEY_LOCAL_MACHINESoftwareMicrosoftTerminal Server Client

This update uses the values of the DblTapDist and DblTapTime settings. These values specify the time and space threshold settings that define consecutive taps or clicks as double-taps or double-clicks. The default value for the DblTapDist setting is 20 pixels, and the default value for the DblTapTime setting is 600 milliseconds. You can optimize these settings for platforms that require more accurate tap or click precision. To optimize these settings, change the DWORD value of the following two registry entries:

• HKEY_CURRENT_USERControlPanelPendblTapDist

• HKEY_CURRENT_USERControlPanelPendblTapTime

Note By default, these registry entries are not present, and you must create them.

Known issue

After you enable this update, consecutive taps or clicks still do not work as intended in an application if the following conditions are true:

• The application is running on the RDP server.

• You want to perform consecutive taps or clicks that are within the values of the DblTapDist andDblTapTime settings in the application.

• You do not want the consecutive taps or clicks to be considered as a double-click.

For example, you want to click two times (such as when you draw two dots in a Microsoft Paint application). The distance between these clicks is less than the value of the DblTapDist setting, and the time between the clicks is less than the value of the DblTapTime setting. In this case, when the EnableDoubleClickDetect value is set, the two clicks are considered as a double-click (or a drag motion in the Microsoft Paint application), instead of the two single clicks that you intended.

Software update information

Download information

The Windows Embedded Compact 7 Monthly Update (February 2013) is now available from Microsoft. To download this Windows Embedded Compact 7 Monthly Update, go to the following Microsoft Download Center website:

Windows Embedded Compact 7 updatesThe kind of processor that each file applies to is visible in the name of each file in the «File information» section.

Prerequisites

This update is supported only if all previously issued updates for this product have also been installed.

Restart requirement

After you apply this update, you must perform a clean build of the whole platform. To do this, use one of the following methods:

• On the Build menu, click Clean Solution, and then click Build Solution.

• On the Build menu, click Rebuild Solution.

You do not have to restart the computer after you apply this software update.

Update replacement information

This update does not replace any other updates.

The English version of this software update package has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Files that are included in this hotfix package

File name	File size	Date	Time	Path
Tscaxctrl.lib	33,719,550	13-Feb-2013	22:35	PublicRdpOakLibArmv5Checked
Tscaxctrl.lib	34,558,602	13-Feb-2013	22:33	PublicRdpOakLibArmv5Debug
Tscaxctrl.lib	25,346,982	13-Feb-2013	22:32	PublicRdpOakLibArmv5Retail
Tscaxctrl.lib	33,720,170	13-Feb-2013	22:50	PublicRdpOakLibArmv6Checked
Tscaxctrl.lib	34,552,978	13-Feb-2013	22:49	PublicRdpOakLibArmv6Debug
Tscaxctrl.lib	25,347,802	13-Feb-2013	22:47	PublicRdpOakLibArmv6Retail
Tscaxctrl.lib	33,609,328	13-Feb-2013	23:06	PublicRdpOakLibArmv7Checked
Tscaxctrl.lib	34,439,052	13-Feb-2013	23:04	PublicRdpOakLibArmv7Debug
Tscaxctrl.lib	25,273,014	13-Feb-2013	23:03	PublicRdpOakLibArmv7Retail
Tscaxctrl.lib	32,119,828	13-Feb-2013	23:21	PublicRdpOakLibMipsiiChecked
Tscaxctrl.lib	34,273,494	13-Feb-2013	23:20	PublicRdpOakLibMipsiiDebug
Tscaxctrl.lib	24,413,776	13-Feb-2013	23:18	PublicRdpOakLibMipsiiRetail
Tscaxctrl.lib	32,135,642	13-Feb-2013	23:36	PublicRdpOakLibMipsii_fpChecked
Tscaxctrl.lib	34,288,886	13-Feb-2013	23:35	PublicRdpOakLibMipsii_fpDebug
Tscaxctrl.lib	24,429,452	13-Feb-2013	23:33	PublicRdpOakLibMipsii_fpRetail
Tscaxctrl.lib	30,053,252	13-Feb-2013	23:51	PublicRdpOakLibSh4Checked
Tscaxctrl.lib	31,872,952	13-Feb-2013	23:50	PublicRdpOakLibSh4Debug
Tscaxctrl.lib	23,203,526	13-Feb-2013	23:48	PublicRdpOakLibSh4Retail
Tscaxctrl.lib	29,789,612	14-Feb-2013	00:06	PublicRdpOakLibX86Checked
Tscaxctrl.lib	29,706,690	14-Feb-2013	00:04	PublicRdpOakLibX86Debug
Tscaxctrl.lib	22,500,614	14-Feb-2013	00:03	PublicRdpOakLibX86Retail

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

References

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Code	Reason
0	No error
1	User-initiated client disconnect.
2	User-initiated client logoff.
3	Your Remote Desktop Services session has ended, possibly for one of the following reasons: The administrator has ended the session. An error occurred while the connection was being established. A network problem occurred. For help solving the problem, see «Remote Desktop» in Help and Support.
260	Remote Desktop can’t find the computer «». This might mean that «» does not belong to the specified network. Verify the computer name and domain that you are trying to connect to.
262	This computer can’t connect to the remote computer. Your computer does not have enough virtual memory available. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support.
264	This computer can’t connect to the remote computer. The two computers couldn’t connect in the amount of time allotted. Try connecting again. If the problem continues, contact your network administrator or technical support.
266	The smart card service is not running. Please start the smart card service and try again.
516	Remote Desktop can’t connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned off 3) The remote computer is not available on the network Make sure the remote computer is turned on and connected to the network, and that remote access is enabled.
522	A smart card reader was not detected. Please attach a smart card reader and try again.
772	This computer can’t connect to the remote computer. The connection was lost due to a network error. Try connecting again. If the problem continues, contact your network administrator or technical support.
778	There is no card inserted in the smart card reader. Please insert your smart card and try again.
1030	Because of a security error, the client could not connect to the remote computer. Verify that you are logged on to the network, and then try connecting again.
1032	The specified computer name contains invalid characters. Please verify the name and try again.
1034	An error has occurred in the smart card subsystem. Please contact your helpdesk about this error.
1796	This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
1800	Your computer could not connect to another console session on the remote computer because you already have a console session in progress.
2056	The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.
2308	Your Remote Desktop Services session has ended. The connection to the remote computer was lost, possibly due to network connectivity problems. Try connecting to the remote computer again. If the problem continues, contact your network administrator or technical support.
2311	The connection has been terminated because an unexpected server authentication certificate was received from the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
2312	A licensing error occurred while the client was attempting to connect (Licensing timed out). Please try connecting to the remote computer again.
2567	The specified username does not exist. Verify the username and try logging in again. If the problem continues, contact your system administrator or technical support.
2820	This computer can’t connect to the remote computer. An error occurred that prevented the connection. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.
2822	Because of an error in data encryption, this session will end. Please try connecting to the remote computer again.
2823	The user account is currently disabled and cannot be used. For assistance, contact your system administrator or technical support.
2825	The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.
3079	A user account restriction (for example, a time-of-day restriction) is preventing you from logging on. For assistance, contact your system administrator or technical support.
3080	The remote session was disconnected because of a decompression failure at the client side. Please try connecting to the remote computer again.
3335	As a security precaution, the user account has been locked because there were too many logon attempts or password change attempts. Wait a while before trying again, or contact your system administrator or technical support.
3337	The security policy of your computer requires you to type a password on the Windows Security dialog box. However, the remote computer you want to connect to cannot recognize credentials supplied using the Windows Security dialog box. For assistance, contact your system administrator or technical support.
3590	The client can’t connect because it doesn’t support FIPS encryption level. Please lower the server side required security level Policy, or contact your network administrator for assistance
3591	This user account has expired. For assistance, contact your system administrator or technical support.
3592	Failed to reconnect to your remote session. Please try to connect again.
3593	The remote PC doesn’t support Restricted Administration mode.
3847	This user account’s password has expired. The password must change in order to logon. Please update the password or contact your system administrator or technical support.
3848	A connection will not be made because credentials may not be sent to the remote computer. For assistance, contact your system administrator.
4103	The system administrator has restricted the times during which you may log in. Try logging in later. If the problem continues, contact your system administrator or technical support.
4104	The remote session was disconnected because your computer is running low on video resources. Close your other programs, and then try connecting again. If the problem continues, contact your network administrator or technical support.
4359	The system administrator has limited the computers you can log on with. Try logging on at a different computer. If the problem continues, contact your system administrator or technical support.
4615	You must change your password before logging on the first time. Please update your password or contact your system administrator or technical support.
4871	The system administrator has restricted the types of logon (network or interactive) that you may use. For assistance, contact your system administrator or technical support.
5127	The Kerberos sub-protocol User2User is required. For assistance, contact your system administrator or technical support.
6919	Remote Desktop cannot connect to the remote computer because the authentication certificate received from the remote computer is expired or invalid. In some cases, this error might also be caused by a large time discrepancy between the client and server computers.
7431	Remote Desktop cannot verify the identity of the remote computer because there is a time or date difference between your computer and the remote computer. Make sure your computer’s clock is set to the correct time, and then try connecting again. If the problem occurs again, contact your network administrator or the owner of the remote computer.
8711	Your computer can’t connect to the remote computer because your smart card is locked out. Contact your network administrator about unlocking your smart card or resetting your PIN.
9479	Could not auto-reconnect to your applications,please re-launch your applications
9732	Client and server versions do not match. Please upgrade your client software and then try connecting again.
33554433	Failed to reconnect to the remote program. Please restart the remote program.
33554434	The remote computer does not support RemoteApp. For assistance, contact your system administrator.
50331649	Your computer can’t connect to the remote computer because the username or password is not valid. Type a valid user name and password.
50331650	Your computer can’t connect to the remote computer because it can’t verify the certificate revocation list. Contact your network administrator for assistance.
50331651	Your computer can’t connect to the remote computer due to one of the following reasons: 1) The requested Remote Desktop Gateway server address and the server SSL certificate subject name do not match. 2) The certificate is expired or revoked. 3) The certificate root authority does not trust the certificate. Contact your network administrator for assistance.
50331652	Your computer can’t connect to the remote computer because the SSL certificate was revoked by the certification authority. Contact your network administrator for assistance.
50331653	This computer can’t verify the identity of the RD Gateway «». It’s not safe to connect to servers that can’t be identified. Contact your network administrator for assistance.
50331654	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address requested and the certificate subject name do not match. Contact your network administrator for assistance.
50331655	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server’s certificate has expired or has been revoked. Contact your network administrator for assistance.
50331656	Your computer can’t connect to the remote computer because an error occurred on the remote computer that you want to connect to. Contact your network administrator for assistance.
50331657	An error occurred while sending data to the Remote Desktop Gateway server. The server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance.
50331658	An error occurred while receiving data from the Remote Desktop Gateway server. Either the server is temporarily unavailable or a network connection is down. Try again later, or contact your network administrator for assistance.
50331659	Your computer can’t connect to the remote computer because an alternate logon method is required. Contact your network administrator for assistance.
50331660	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server address is unreachable or incorrect. Type a valid Remote Desktop Gateway server address.
50331661	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
50331662	Your computer can’t connect to the remote computer because the Remote Desktop Services client component is missing or is an incorrect version. Verify that setup was completed successfully, and then try reconnecting later.
50331663	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is running low on server resources and is temporarily unavailable. Try reconnecting later or contact your network administrator for assistance.
50331664	Your computer can’t connect to the remote computer because an incorrect version of rpcrt4.dll has been detected. Verify that all components for Remote Desktop Gateway client were installed correctly.
50331665	Your computer can’t connect to the remote computer because no smart card service is installed. Install a smart card service and then try again, or contact your network administrator for assistance.
50331666	Your computer can’t stay connected to the remote computer because the smart card has been removed. Try again using a valid smart card, or contact your network administrator for assistance.
50331667	Your computer can’t connect to the remote computer because no smart card is available. Try again using a smart card.
50331668	Your computer can’t stay connected to the remote computer because the smart card has been removed. Reinsert the smart card and then try again.
50331669	Your computer can’t connect to the remote computer because the user name or password is not valid. Please type a valid user name and password.
50331671	Your computer can’t connect to the remote computer because a security package error occurred in the transport layer. Retry the connection or contact your network administrator for assistance.
50331672	The Remote Desktop Gateway server has ended the connection. Try reconnecting later or contact your network administrator for assistance.
50331673	The Remote Desktop Gateway server administrator has ended the connection. Try reconnecting later or contact your network administrator for assistance.
50331674	Your computer can’t connect to the remote computer due to one of the following reasons: 1) Your credentials (the combination of user name, domain, and password) were incorrect. 2) Your smart card was not recognized.
50331675	Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not listed in the RD Gateway’s permission list 2) You might have specified the remote computer in NetBIOS format (for example, computer1), but the RD Gateway is expecting an FQDN or IP address format (for example, computer1.fabrikam.com or 157.60.0.1). Contact your network administrator for assistance.
50331676	Remote Desktop can’t connect to the remote computer «» for one of these reasons: 1) Your user account is not authorized to access the RD Gateway «» 2) Your computer is not authorized to access the RD Gateway «» 3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password) Contact your network administrator for assistance.
50331679	Your computer can’t connect to the remote computer because your network administrator has restricted access to this RD Gateway server. Contact your network administrator for assistance.
50331680	Your computer can’t connect to the remote computer because the web proxy server requires authentication. To allow unauthenticated traffic to an RD Gateway server through your web proxy server, contact your network administrator.
50331681	Your computer can’t connect to the remote computer because your password has expired or you must change the password. Please change the password or contact your network administrator or technical support for assistance.
50331682	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance.
50331683	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server does not support the request. Contact your network administrator for assistance.
50331684	Your computer can’t connect to the remote computer because the client does not support one of the Remote Desktop Gateway’s capabilities. Contact your network administrator for assistance.
50331685	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server and this computer are incompatible. Contact your network administrator for assistance.
50331686	Your computer can’t connect to the remote computer because the credentials used are not valid. Insert a valid smart card and type a PIN or password, and then try connecting again.
50331687	Your computer can’t connect to the remote computer because your computer or device did not pass the Network Access Protection requirements set by your network administrator. Contact your network administrator for assistance.
50331688	Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Contact your network administrator for assistance.
50331689	Your computer can’t connect to the remote computer because the RD Gateway server that you are trying to connect to is not allowed by your computer administrator. If you are the administrator, add this Remote Desktop Gateway server name to the trusted Remote Desktop Gateway server list on your computer and then try connecting again.
50331690	Your computer can’t connect to the remote computer because your computer or device did not meet the Network Access Protection requirements set by your network administrator, for one of the following reasons: 1) The Remote Desktop Gateway server name and the server’s public key certificate subject name do not match. 2) The certificate has expired or has been revoked. 3) The certificate root authority does not trust the certificate. 4) The certificate key extension does not support encryption. 5) Your computer cannot verify the certificate revocation list. Contact your network administrator for assistance.
50331691	Your computer can’t connect to the remote computer because a user name and password are required to authenticate to the Remote Desktop Gateway server instead of smart card credentials.
50331692	Your computer can’t connect to the remote computer because smart card credentials are required to authenticate to the Remote Desktop Gateway server instead of a user name and password.
50331693	Your computer can’t connect to the remote computer because no smart card reader is detected. Connect a smart card reader and then try again, or contact your network administrator for assistance.
50331695	Your computer can’t connect to the remote computer because authentication to the firewall failed due to missing firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance.
50331696	Your computer can’t connect to the remote computer because authentication to the firewall failed due to invalid firewall credentials. To resolve the issue, go to the firewall website that your network administrator recommends, and then try the connection again, or contact your network administrator for assistance.
50331698	Your Remote Desktop Services session ended because the remote computer didn’t receive any input from you.
50331699	The connection has been disconnected because the session timeout limit was reached.
50331700	Your computer can’t connect to the remote computer because an invalid cookie was sent to the Remote Desktop Gateway server. Contact your network administrator for assistance.
50331701	Your computer can’t connect to the remote computer because the cookie was rejected by the Remote Desktop Gateway server. Contact your network administrator for assistance.
50331703	Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is expecting an authentication method different from the one attempted. Contact your network administrator for assistance.
50331704	The RD Gateway connection ended because periodic user authentication failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance.
50331705	The RD Gateway connection ended because periodic user authorization failed. Try reconnecting with a correct user name and password. If the reconnection fails, contact your network administrator for further assistance.
50331707	Your computer can’t connect to the remote computer because the Remote Desktop Gateway and the remote computer are unable to exchange policies. This could happen due to one of the following reasons: 1. The remote computer is not capable of exchanging policies with the Remote Desktop Gateway. 2. The remote computer’s configuration does not permit a new connection. 3. The connection between the Remote Desktop Gateway and the remote computer ended. Contact your network administrator for assistance.
50331708	Your computer can’t connect to the remote computer, possibly because the smart card is not valid, the smart card certificate was not found in the certificate store, or the Certificate Propagation service is not running. Contact your network administrator for assistance.
50331709	To use this program or computer, first log on to the following website: <a href=»»></a>.
50331710	To use this program or computer, you must first log on to an authentication website. Contact your network administrator for assistance.
50331711	Your session has ended. To continue using the program or computer, first log on to the following website: <a href=»»></a>.
50331712	Your session has ended. To continue using the program or computer, you must first log on to an authentication website. Contact your network administrator for assistance.
50331713	The RD Gateway connection ended because periodic user authorization failed. Your computer or device didn’t pass the Network Access Protection (NAP) requirements set by your network administrator. Contact your network administrator for assistance.
50331714	Your computer can’t connect to the remote computer because the size of the cookie exceeded the supported size. Contact your network administrator for assistance.
50331716	Your computer can’t connect to the remote computer using the specified forward proxy configuration. Contact your network administrator for assistance.
50331717	This computer cannot connect to the remote resource because you do not have permission to this resource. Contact your network administrator for assistance.
50331718	There are currently no resources available to connect to. Retry the connection or contact your network administrator.
50331719	An error occurred while Remote Desktop Connection was accessing this resource. Retry the connection or contact your system administrator.
50331721	Your Remote Desktop Client needs to be updated to the newest version. Contact your system administrator for help installing the update, and then try again.
50331722	Your network configuration doesn’t allow the necessary HTTPS ports. Contact your network administrator for help allowing those ports or disabling the web proxy, and then try connecting again.
50331723	We’re setting up more resources, and it might take a few minutes. Please try again later.
50331724	The user name you entered does not match the user name used to subscribe to your applications. If you wish to sign in as a different user please choose Sign Out from the Home menu.
50331725	Looks like there are too many users trying out the Azure RemoteApp service at the moment. Please wait a few minutes and then try again.
50331726	Maximum user limit has been reached. Please contact your administrator for further assistance.
50331727	Your trial period for Azure RemoteApp has expired. Ask your admin or tech support for help.
50331728	You no longer have access to Azure RemoteApp. Ask your admin or tech support for help.

The “Cannot run this application on my computer” message is more common than you might think, but should not be considered a default error within the Windows 10 operating system .

The new version of Microsoft software is recognized for its new security methods, which improve the user experience on your computer.

Since the error is caused by common reasons, the solutions are quite simple and easy to perform, even for those who do not have experience with a computer.

Through the simple methods that will be explained below, you will be able to run the program with complete comfort, ensuring that the error will not appear on the screen again.

Reasons why “This application cannot be run on the computer” appears on the PC

The problem can be reduced to a compatibility error with the operating system or the operating methodology of the computer. So it is decided to block it automatically.

However, this should not be a cause for concern. Well, one of the benefits of Windows is the simplicity with which you can solve each of your problems.

So for every situation there is a way to make the program in question operational.   Thus achieving the completion of the task that each person wants to do.

Therefore, we advise you to follow each of the indications set forth in this article to the letter. In order to continue enjoying the experience with Windows 10.

List of solutions for the error “Cannot run this application on the computer”

Clearly there are multiple reasons why this message can appear on your screen, therefore it is essential to identify which is the cause that best fits the situation you suffer. Since the application has just been installed on the computer, the modifications must be made directly to the equipment.

Check the software version

We all know that the programs that are installed on devices have versions. Which serve to offer improvements to those who decide to use it.

Because of this, there is a possibility that the update number you have installed on your computer is not the most recent, thus causing compatibility problems. Therefore, it is advisable to make sure you purchase the latest version released by the programmers. In order to avoid this type of situation.

Verify compatibility with the system

Continuing with the theme of the versions, but this time in bits. There are programs that work exclusively for the person who owns the computer.

The appearance of messages such as “Cannot run this application on the computer” may be caused by installing the wrong version for the system.

It is advisable to verify what type of architecture the computer works with through its properties (either 32-bit or 64-bit). In order to download the appropriate and compatible one with the equipment, thus avoiding this type of errors.

Direct problems with the application

A situation that directly affects the downloaded program can also cause these types of errors. So you can try the following solutions:

Try re-downloading the file itself, in case a connection problem caused a failure. You can also try to run the application from the disk drive system, directly executing the file with an EXE extension.

Similarly, running the shortcut as administrator may also work . In case it is related to the permissions granted by the system towards the application.

In conclusion, you should not worry about the error of “Cannot run this application on the computer”. Whatever appears instead of the program’s operating window.

Whether it’s by means of system protection or a simple software glitch, there are many ways to fix this type of situation. Therefore, you only have to follow each of the indications mentioned in this space so that you can enjoy the functions that Windows has to offer.

Некоторые программы, такие как online-игры и специализированный софт, отказываются запускаться на виртуальной машине. Как я понял, программа проверяет некоторые признаки виртуально машины (имена вендоров, VID/PID оборудования и т.д.) и найдя совпадение пишет что-то типа «Sorry, this application cannot run under a virtual machine». Ниже небольшой мануальчик по обходу детекта виртуальной машины для VMware Workstation. Не ручаюсь что на 100% рабочий, потому что вариантов определения виртуалки вагон и маленькая тележка, но самые распространенные проверки он обходит.

Для обхода детектирования виртуальной машины нам понадобятся:

• VMware Workstation v 12.1.0 build 3272444
• Пропатченый файл vmware-vmx.exe с изменными вендорами. Образ BIOS из которого были убраны строки с «VMware» и добавлен серийный номер материнской платы. Скачать можно отсюда.
• Прямые руки.

1. Устанавливаем VMware Workstation. Правилами хостинга запрешено публиковать ломанный софт, можете зайти на самый большой русскоязычный торрент трекер — там есть. Версия нужна 12.1.0 build 3272444, потому что патченный exe-файлик данной версии. Можете попробовать другую на свой страх и риск.

2. Создаем виртуальную машину и устанавливаем на неё операционную систему. Ваш покорный слуга использовал Windows 7, она работает стабильнее и менее требовательна к ресурсам.

3. Устанавливаем VMware Tools. Запускаем виртуальную машину. Далее идем «Виртуальная машина» —> «Установить пакет VMware Tools… «. В виртуальной машине появляется CD с установщиком. Запускаем программу установки, устанавливаем с настройками по умолчанию.

4. Меняем vmware-vmx.exe на файл из архива. (Путь по умолчанию: C:Program Files (x86)VMwareVMware Workstationx64vmware-vmx.exe)

5. Копируем образ BIOS в папку с виртуальной машиной. Можно скопировать в другую папку, только тогда в файле настроек нужно прописывать полный путь к файлу.

6. Правим файл с настройками виртуальной машины (файл с расширением .vmx) любым текстовым редактором. Добавляем строки:

---

monitor_control.restrict_backdoor = «true»
cpuid.1.ecx=»0—:—-:—-:—-:—-:—-:—-:—-«
bios440.filename = «6006.ROM»
isolation.tools.copy.disable = «TRUE»
isolation.tools.dnd.disable = «TRUE»
isolation.tools.paste.disable = «TRUE»

---

7. Устанавливаем нужную программу и пробуем запустить.

Обратите внимание, что пакет VMware Tools нужно установить ДО замены exe-файла и правки настроек виртуальной машины. В противном случае установщик скажет, что его нужно ставить только на виртуальную машину и отменит установку. А без установленного пакета недоступны некоторые важные функции, например, работа с 3D графикой.

БОльшая часть информации и файлы взяты отсюда. За что автору огромное спасибо!)

Сообщение скорее всего выглядит вот так:

1. Самое очевидное: вы действительно запустили клиент на виртуальной машине.
Как решить: Не надо так.

2. Антивирусная программа посчитала файлы игры подозрительными и запустил приложение в защищённой среде, т.е. в той же самой виртуальной машине.
Как решить: Добавить игру в исключения антивируса.

3. Проблема может быть решена изменением данных в реестре:

Не забудьте перезагрузить компьютер после изменений.

4. Если имя ПК установлено по умолчанию.
Как решить: изменить имя ПК

How to fix «This Application cannot run under a Virtual Machine» [solved] from treeofsavior

Не забудьте перезагрузить компьютер после изменений.

5.

Если вы используете ОС Windows 8/8.1, необходимо

отключить

компонент Hyper-V.
Для этого:
На панели управления выберите элемент Программы, а затем — Программы и компоненты.
Выберите Включение или отключение компонентов Windows.
Снимите галочку с пункта Hyper‑V, нажмите кнопку ОК, а затем кнопку Закрыть.
Перезагрузите ваш компьютер.

6. На панели управления выберите элемент Программы, а затем — Программы и компоненты.
Выберите Включение или отключение компонентов Windows.
Разворачиваем «.Net Framework 3.5 (включает .Net 2.0 и 3.0)
И снимаем галки с «Активация Windows Communication Foundation не по HTTP» и с «Активация Windows Communication Foundation по HTTP»

7. Если вы используете ОС Windows 8/8.1, необходимо

включить и отключить

компонент Hyper-V.
Для этого:
На панели управления выберите элемент Программы, а затем — Программы и компоненты.
Выберите Включение и затем отключение компонентов Windows.
Поставьте галочку на пункт Hyper‑V, нажмите кнопку ОК, а затем кнопку Закрыть.
Перезагрузите ваш компьютер.

8. Редкий вариант. Отключение виртуализации на уровне BIOS.
Как решить: следовать инструкции, но отключить, а не включить виртуализацию https://www.isumsoft.com/computer/enable-virtualization-technology-vt-x-in-bios-or-uefi.html

Нашли другое решение? Напишите в комментарии. Это будет полезно другим с подобной проблемой.

• #2

Сталкивался с этой проблемой, не помог не один способ описанный выше. Возникает он если у вас на ПК хоть раз были программы, создающие виртуальную среду — разнообразные эмуляторы андроидов, смартфонов или ПК. Даже если удалить эти программы и почистить комп, следы от них все равно остаются, самое радикальное — переустановить винду. Мне, однако, помог способ, в котором нужно зайти в BIOS, и найти настройку связанную с возможностью запуска виртуальной среды на ПК, в разных версиях BIOSa эта настройка называется по разному, ищите по ключевым словам — Virtualization, VM, Cloud space и так далее. Чтобы эта ошибка прекратила появляться, нужно чтобы эти функции были выключены в Биосе — положение «Disabled”

Skip to content

Часто случается, что при запуске какого-либо вин-приложения из-под виртуальной машины приложение мгновенно закрывается с такой вот ошибкой:

Sorry, this application cannot run under a Virtual Machine

Это в основном означает, что разработчики данного приложения пожелали не давать ему возможности запускаться из-под виртуалок.

Исследовав проблему, нашел её решение для VMWare — оно состоит в том что необходимо подправить конфиг файла с расширением .vmx, дописав туда несколько строчек:

isolation.tools.getPtrLocation.disable = "TRUE"
isolation.tools.setPtrLocation.disable = "TRUE"
isolation.tools.setVersion.disable = "TRUE"
isolation.tools.getVersion.disable = "TRUE"
monitor_control.disable_directexec = "TRUE"
monitor_control.disable_chksimd = "TRUE"
monitor_control.disable_ntreloc = "TRUE"
monitor_control.disable_selfmod = "TRUE"
monitor_control.disable_reloc = "TRUE"
monitor_control.disable_btinout = "TRUE"
monitor_control.disable_btmemspace = "TRUE"
monitor_control.disable_btpriv = "TRUE"
monitor_control.disable_btseg = "TRUE"

А кто-то советует дописать чуть другое:

monitor_control.virtual_rdtsc = "false"
monitor_control.restrict_backdoor = "true"
isolation.tools.getPtrLocation.disable = "true"
isolation.tools.setPtrLocation.disable = "true"
isolation.tools.setVersion.disable = "true"
isolation.tools.getVersion.disable = "true"
monitor_control.disable_directexec = "true"

В обоих случаях мне удалось обойти защиту приложений и запустить их из под виртуальной машины!

UPD: Для смены мака и других свойств виртуальной машины — пробуем также VmTweaker — http://sourceforge.net/projects/vmtweaker/

Некоторые советуют ставить VirtualBox вроде в нем с этим нет проблем. Я лично не пробовал.

After installing Hyper-V in the windows, I get the following error for running a game in my windows. Of course I am not running it in the virtual machine. I want to run the game in the PC itself that I installed the Hyper-V.

sorry, this application cannot run under a virtual machine

Even I tried to stop the Hyper-V service inside the Hyper-V management but that doesn’t work for me and I get the same error. Please help me find a solution to this.

Thanks.

asked Mar 13, 2012 at 12:48

2

I found a good solution. making an entry in the boot loader, so that the hypervisor will not start by choosing that option while restarting the system. here is the steps to this:

1.At the command prompt, type the following:

bcdedit /copy {default} /d "No Hypervisor"

2.The above command should say: The entry was successfully copied to {guid}.
Copy that guid to the clipboard including the curly braces.

3.Now, type the following command:

bcdedit /set {guid} hypervisorlaunchtype off

In the above command, replace {guid} with what you copied in step 2.
I found the solution here : Hyper-V and VMware Workstation on the same computer.
It works for me and I hope it will works for people having the same problem.

answered Mar 17, 2012 at 22:32

AMCodedAMCoded

1,3362 gold badges22 silver badges38 bronze badges

This is the game copy-protection trying to stop you from running the game in a sandbox such as a virtual machine, where you’d be able to automate (bot) the game or hack the game by poking memory from outside of the machine.

The only way to resolve this issue is for you to either

A) Uninstall VirtualPC/Hyper-V completely

B) Ask the game company to change their policy, explaining precisely why you need Hyper-V and would like to play their game on the same machine, and wait for them to push out an update.

answered Mar 13, 2012 at 17:10

SecurityMattSecurityMatt

6,4651 gold badge21 silver badges28 bronze badges

2

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

>I’ve seen this application work under Parallels so can anybody tell me what the above error actually means?

It means the developer is a bonehead and put in an explicit check for virtualization, e.g. a blue pill check. If this software works in Parallels, there’s a good chance bypassing that alert would make it work in Fusion and Workstation 6. Maybe the developer was pestered by user asking for support in a VM that s/he put in the alert in on-purpose? Either way it’s a bad move. Your best bet is contacting the developer and asking for a workaround.

I found the software here: http://www.odeon.cn/ and version 1.98.6 contains that alert. I could find no obvious registry and/or file check using regmon/filemon where the developer is looking specifically for VMware but whatever criteria the check is based on, it must work on multiple host platforms.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I worked on an app once that checked to see if it was running on a VM. They actually had a fairly good reason for doing it…

You can find samples of code on the web for making this check. It typically consists of executing an illegal instruction, then examining the exception stack. Or something like that. The routine was pre-cooked, and I really didn’t spend much time looking at exactly what it was doing. In any case, not only was the routine able to determine whether it was running virtual, it could also tell you whether it was running under VMware, VirtualPC or Parallels.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Well my question is that does Fusion then itself depend on the _wording_ and _format_ of the exception stack? If not then it might be possible the twart these checks by rewriting it. so an option could be provided that allows me to «hide» from an application that’s using it to check etc etc.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Well my question is that does Fusion then itself

depend on the _wording_ and _format_ of the exception

stack? If not then it might be possible the twart

these checks by rewriting it. so an option could be

provided that allows me to «hide» from an application

that’s using it to check etc etc.

Well….I think that is the wrong approach to the problem. The problem is not with Fusion but rather with the application itself. So any fix should go into the application itself. If you start tweaking Fusion in order to get around that, then a different approach will be used by the next application which requires a different workaround in Fusion and so on.

As Richard already indicated in his previous post…contact the developer…

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Yeah that would seem fair however my response was making the assumption that this and only this would be the way developers can check if you’re running in a virtual machine. I suppose there are other ways too. I don’t expect to get much help from the developer.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I don’t expect to get much help from the

developer.

Well…I do not know that specific application and what it does but are there any alternatives you can use instead if the developer really does not want to provide any workarounds?

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

There are actually a bunch of ways to check if you’re running in a VM. For example, once you install tools, the name of the network adapter in Windows is «VMware Accelerated AMD PCNet». In Linux the video card is detected as a VMware video adapter. IIRC the BIOS is named something VMware related. And so on. I’m sure there are similar easy checks for other virtualization software.

It’s akin to a program refusing to run on certain motherboards — there’s generally no valid reason to do this (drbanks, I’m curious what reason you had). The only reason I can come up with is the developer is paranoid about reverse-engineering or doesn’t want users to get around copy protection (and I don’t think these are really good reasons).

While technically[/i] it’s possible for VMware to play the arms race, it’d be a bad idea in terms of stability and ultimately it’s a problem with the developer of the uncooperative software.

Edited to include paranthetical notes —etung 2007.03.04 10:48

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Why does virtualization make it easier to circumvent copy protection?

The same way that setting breakpoints or running a program in a debugger would make it easier — it’s then possible to examine memory state. Some viruses, for example, won’t run if a debugger is present in order to make it harder for antivirus writers to figure out what’s going on. Note that it’s still not easy to do, just something a determined attacker might use.

From what you’ve said about JAF, I don’t see any reason it shouldn’t be able to run in a VM.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

As for why do this…

I’m not sure about the state of the NDAs, so I won’t be specific, but:

The particular application had to lock down the desktop and control all access to the outside world. Think of it as a kiosk-like application. It would have hardly been appropriate to allow the application to be run under a VM, where the user could access anything and everything in the real world on the host computer. So basically, the entire sandbox we tried so hard to create would be mooted if it were allowed to be run virtualized.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

If you think about if you can tell you are running under virtualization then it’s not true virtualization.

A lot of what I described isn’t determining that you’re running in a virtual environment, it’s determining your hardware happens to match what a known virtual environment looks like. Also, once you start involving the real world (e.g. the network, unless you virtualize that too), it’s possible via timing attacks.

drbanks: Hmm, I hadn’t considered a security app. Thanks for pointing out this use case. However, I agree only from a developer perspective — as a user, I might not consider this a good thing

Edited to include question about user’s perspective. —etung 2007.03.05 20:25

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I’m not admitting to violating traffic laws but I have seen Defensive Driving applications that have tried to ‘lock’ my friend’s[/i] computer, of course they lock friend’s[/i] VM’s instead.

Also I have beta tested software that attempts to DRM-lock Office documents like Word, Excel, Adobe Acrobat, etc. They even went so far as to hook keyboard interrupts and lock the video frame buffers somehow. Luckily I screenshotted away from the host during the beta to demonstrate actual bugs not the ‘breaking’ of their technologies (which I also was successful in, btw). Needless to say the quickly became aware of the reality of virtualization.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

There’s a security researcher that claims Intel VT and AMD-V can be used to make a perfectly undetectable ring -1 environment. Assuming there are no ‘give-away’ devices, drivers or registry entries. It might be possible to conjure an undetectable ring 0 — ring 3 working set. In practice such an x86 black box is impractical because you’ll always want to accelerate, trap and emulate, enlighten or paravirtualize some aspect of x86 and that will be your poker tell.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Out of interest try opening the VMX file associated with the virtual machine. Try adding the following line to it:

monitor_control.restrict_backdoor = TRUE[/code]

The VMware tools won’t function but it may stop the software detecting the fact that it is running in a VM. If it doesn’t work, just power off the VM and remove the line from the VMX file.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

You should try capturing the install on a non-virtual Win OS using something like Altiris’s SVS, then once you have it captured, you then can export the layer, and import the layer on your Virtual OS via SVS again. This should get around this problem, that is unless the process/application checks for virtualization when it is ran.