Search This Blog

Loading...

Tuesday, May 24, 2016

This app can't open. App can't be opened using the Built-in Administrator account.

The error message, "This app can't open.  App can't be opened using the Built-in Administrator account." is not a normal error message one would encounter in the use of their Windows 8/Windows 10 computer.  This issue is likely being manufactured by someone who modified Windows 8/Windows 10 by Disabling EnableLUA without a complete understanding of User Account Control and Admin Approval Mode.  To quote the popular website Windows IT Pro, "This is not a supported state of the OS and will block the modern applications-- so don't do this."

EnableLUA controls not only User Account Control but also Admin Approval Mode.  By default in Windows 8/Windows 10, EnableLUA is Enabled.  On the internet, there is the mistaken belief that setting EnableLUA to Disabled is an inocuous registry setting one can use to Disable User Account Control.  This is incorrect.  If EnableLUA is set to Disabled then Admin Approval Mode is Disabled which results in the error message: "This app can't open.  App can't be opened using the Built-in Administrator account."  Therefore, it can be understood that setting EnableLUA to Disabled results in functionality within Windows 8/Windows 10 to no longer function.  This includes built-in apps like Microsoft Edge, Clock, Calculator but also Control Panels like the Windows 10 Settings Control Panel.  Ultimately, it is a terrible idea to Disable EnableLUA because it impacts not just User Account Control but also Admin Approval Mode.

The proper method to disable User Account Control is to drag the User Account Control slider to Never Notify.  Dragging the User Account Control slider to Never Notify does not change EnableLUA from 1 to 0 therefore allowing Windows 8/Windows 10 to continue to function as it was designed by Microsoft.

To return Windows 8/Windows 10 to normal functionality:
  1.   Click Start - Run.

  2.   Type: regedit

  3.   Click OK.

  4.   Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Current Version\Policies\System

  5.   If it does not exist, create a new DWORD (32-bit value) entitled EnableLUA and set the value to: 1

  6.   If it does not exist, create a new DWORD (32-bit value) entitled FilterAdministratorToken and set the value to: 0

  7.   If it does not exist, create a new DWORD (32-bit value) entitled ConsentPromptBehaviorAdmin and set the value to: 5

  8.   If it does not exist, create a new DWORD (32-bit value) entitled ConsentPromptBehaviorUser and set the value to: 1

  9.   Reboot.
This issue has been resolved.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Friday, April 22, 2016

The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.

You may encounter the following error message when using the L2TP/IPSec VPN Client that is native to the Windows Operating System: "The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer."  This error message typically occurs when you are using the wrong Pre-Shared Key for your L2TP VPN.  This error message can occur when other components of your configuration are incorrect but the first thing to confirm is that you are using the correct Pre-Shared Key.

If you are using the wrong Pre-Shared Key, the L2TP VPN connection will say Connecting for a long period of time and then display the error message: "The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer."

If you are using the wrong username or password, the L2TP VPN will immediately respond with: "The remote connection was denied because the user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server."

If you are using the correct username, password and pre-shared key, the VPN connects immediately.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Wednesday, September 16, 2015

How do you Remote Desktop to a computer using an L2TP VPN?

To Remote Desktop to a computer using an L2TP VPN:

These steps may be slighly different on your computer depending upon which version of Windows you are using.
  1. Click Start - All Programs.

  2. Click Accessories.

  3. Click Remote Desktop Connection.

  4. In the Computer field, enter the IP Address of the computer or the Fully Qualified Domain Name (FQDN) of the computer you wish to control.

  5. Click Connect.

  6. Enter the username and password you use to login to the computer.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you disconnect from an L2TP VPN using Microsoft Windows?

To disconnect from an L2TP VPN using Microsoft Windows:

These steps may be slightly different on your computer depending upon which version of Windows you are using.
  1. Click Start - Control Panel.

  2. Click Network and Sharing Center.

  3. Click Change Adapter Settings.

  4. Double-click the VPN Connection.

  5. Click Disconnect.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you connect to an L2TP VPN using Microsoft Windows?

To connect to an L2TP VPN using Microsoft Windows:

These steps may be slighly different on your computer depending upon which version of Windows you are using.
  1. Click Start - Control Panel.

  2. Click Network and Sharing Center.

  3. Click Change Adapter Settings.

  4. Double-click the VPN Connection.

  5. Click Connect.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you setup L2TP VPN Windows Domain DNS using the Watchguard XTM-25 Web UI?

To setup L2TP VPN Windows Domain DNS using the Watchguard XTM-25 Web UI:
  1. Browse to the Watchguard XTM Web UI.

  2. Click Network.

  3. Click Interfaces.

  4. Below DNS Servers in the DNS Server field, enter the IP Address of the Windows Domain Controller.  Insure this IP Address is the first in the list.

  5. Below this, enter the Primary and Secondary DNS Servers from your ISP.

  6. Click Save. 
When connected to the L2TP VPN, you will have to use the Fully Qualified Domain Name (FQDN) ala host.domain.suffix to access the Computer inside the Windows Domain.  Example: computer01.mydomain.com.  

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you configure wireless using the Watchguard XTM-25 Web UI?

To configure wireless using the Watchguard XTM-25 Web UI:
  1.  Browse to the Watchguard XTM Web UI. 

  2. Click Network.

  3. Click Wireless.

  4. Select Enable Wireless.

  5. Select Enable Wireless Access Points.

  6. Click Configure next to Access Point 1 Enabled.

  7. Click Enable Access Point 1.

  8. From interface type drop down list, select Optional.

  9. In the IP Address field, enter the IP Address.

  10. Below Address Pool, click add and enter the Start IP and End IP.

  11. Click the Wireless tab.

  12. In the Network Name (SSID) field, enter the SSID.

  13. From the Encryption drop-down list, select WAP/WAP2 (PSK).

  14. In the Passphrase field, enter the passphrase.

  15. Click the DNS/WINS tab.

  16. In the DNS Server field, enter the DNS Server IP Address.

  17. Click Add.

  18. Click Return to Main Page.

  19. Click Save.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

How do you create a Watchguard L2TP VPN adapter using Microsoft Windows?

To create a Watchguard L2TP VPN adapter using Microsoft Windows:

These steps may be slighly different on your computer depending upon which version of Windows you are using.
  1. Click Start - Control Panel.

  2. Click Network and Sharing Center.

  3. Click Setup a new connection or network.

  4. Select Connect to a workplace.

  5. If prompted, select No create a new connection.

  6. Click Next.

  7. Select Use my Internet connection (VPN).

  8. In the Internet Address field, type the Public IP Address of the Watchguard.

  9. In the Destination field, give the connection a name.

  10. If it is visible at the bottom, check the field that says Don't connect now; just set it up so I can connect later.

  11. Click Create.

  12. Click Change Adapter Settings.

  13. Right-mouse click the connection you have created and select Properties.

  14. Click the Security tab.

  15. From the drop down list below Type of VPN, select Layer 2 Tunneling Protocol with IPsec (L2TP/IPsec).

  16. Click Advanced Settings.

  17. Select Use preshared key for authentication.

  18. In the Key field, enter the preshared key.

  19. Click OK.

  20. Click OK.
Please do not remove or delete this VPN connection.

If you found this information helpful, please consider linking to Eugene Computer Services.

Donations are greatly appreciated.

Subscribe to: Posts (Atom)

Legal Notice

Alan Curtis provides programming examples and technical information for illustration only without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose.

Alan Curtis does not assume any legal liability or responsibility for the accuracy and/or completeness of the information provided. Alan Curtis will not be held liable for any direct or indirect loss or damage arising under this legal notice or in connection with the use of this website. Alan Curtis is not affiliated with Microsoft, Yahoo and Google. All trademarks and copyrighted material are the property of their respective owners.

The opinions expressed by Alan Curtis on this blog is based upon information he considers reliable but is not warranted for its completeness or accuracy and should not be relied upon as such. Alan Curtis' statements and opinions are subject to change without notice.

The entire contents of this blog has been copyrighted by Alan Curtis unless otherwise indicated. All rights are reserved by Alan Curtis and content may not be reproduced, downloaded, disseminated, published, or transferred in any form or by any means, except with the prior written permission of Alan Curtis.