Logo

Something went wrong, We couldn’t start

There are instances when you might encounter an error that says, “Something went wrong, We couldn’t start your program” when you open any Office program. This could be due to an issue with the Office file and any Office app you open throws the same error message. This applies to Office 2019/2016, Office 365 Home, Office for Business as well as Business editions. In this post, you will be guided in what you can do to resolve this error.

There are several potential fixes for this error, you might only have to restart your computer or you may have to repair Office from Apps and Features or you could also uninstall and install it back again. For more details, follow each one of the provided options below.

Option 1 – Restart your computer

You might be unable to launch any Office app due to some background process that got stuck or there might be some glitch in the system. Thus, the first thing you can do to resolve the error is simply restarting your computer. Once you’ve restarted your computer, open the Office app again or you could also try to sign in back with your Microsoft account that’s connected to Office. If you’re not quite sure which account you were using, you can follow these steps:

  • Open any Office app.
  • Then click on File and look for your name located in the top-right portion.
  • Now click on it. This will display the email or Microsoft account that’s related to Office.

Option 2 – Try repairing Office from Apps and Features

Since Windows 10 offers some repair features that could replace some of the core files with the original files, you can take advantage of such a feature to fix the “Something went wrong, We couldn’t start your program” error when opening any Office app.

  • Open Windows settings and click the Apps and Features option.
  • Next, scroll down until you see the Microsoft Office installation option. Select it and click on Modify.
  • This will open a window and from there, select Quick Repair or Online Repair and click on the Repair button.

Note: When you choose to repair, you might be given two options which depend on how Microsoft Office was installed. For instance, it was installed via Web Installer or Offline Installer (MSI-based). In Web Installer, select Online Repair > Repair when you’re prompted on how you would like to repair Office. While in MSI-based, you have to select Repair under “Change your installation” and then click on Continue. The repair process makes sure that the app data remains untouched.

Option 3 – Try to uninstall and reinstall Office

If neither of the two given options above worked, then you might want to uninstall Office and reinstall it. All you have to do is download the Microsoft Office Uninstall tool from the official site of Microsoft and run it. This will remove any incomplete Office installation as well as unwanted files. It will also get rid of all the Office apps and settings on your computer.

Do You Need Help with Your Device?

Our Team of Experts May Help
Troubleshoot.Tech Experts are There for You!
Replace damaged files
Restore performance
Free disk space
Remove Malware
Protects WEB browser
Remove Viruses
Stop PC freezing
GET HELP
Troubleshoot.Tech experts work with all versions of Microsoft Windows including Windows 11, with Android, Mac, and more.

Share this article:

You might also like

Setup has failed to determine install choices
Running the Windows Setup does not always go smoothly as you could encounter some errors along the way. One of these errors is the “Something happened, Setup has failed to determine supported install choices” error. The only given option in such cases is to click the Close button and exit the setup. This kind of error in Windows setup can occur when you try to downgrade to the previous version of Windows using the built-in mechanism. This error could be caused by a corrupted image or it is also possible that the set of files are incomplete. Aside from that, it could also be due to compatibility issues or that the module used to downgrade the Windows operating system is not configured properly. To fix this error, you have to run the Windows Setup program in compatibility mode so that you can downgrade Windows. You could also use the image for the lower version of Windows that’s available on the official site of Microsoft. But before you do any of these, make sure that you’re logged in as an administrator. To fix the “Something happened, Setup has failed to determine supported install choices” error, follow the given options below sequentially.

Option 1 – Try to run the Installer of the downgraded version in Compatibility Mode

This is the first thing you can try to resolve the issue instead of going right ahead on making a bootable device. So if you are downgrading Windows, you can try to run the installer in the compatibility mode for that specific Windows version.
  • Look for the setup file.
  • Once you find it, right-click on it and select Properties from the context menu.
  • After that, go to the Compatibility tab and mark the checkbox for “Run this program in compatibility mode for:” and from the drop-down list, select either Windows 7 or Windows 8.
  • You also have to check the “Run as administrator” option.
  • Now click the Apply button and then click OK to save the changes made and check if it has resolved the issue or not.

Option 2 – Try to troubleshoot compatibility

This option is almost the same as the first one except it is an alternative way of fixing the “Setup has failed to determine supported install choices” error in case the first one didn’t work. In this option, you will troubleshoot the compatibility issue.
  • Look for the setup file.
  • Then right-click on it and select the “Troubleshoot compatibility” from the context menu.
  • After that, click on the “Try recommended setting” option. Once the process is done, the error message should be gone.

Option 3 – Run the DISM tool

You can run the DISM tool as well to help fix the error code 0x80244022 during Windows Update. Using this built-in tool, you have various options such as the “/ScanHealth”, “/CheckHealth”, and “/RestoreHealth”.
  • Open the Command Prompt with admin privileges.
  • Then type in the following commands and make sure to hit Enter right after you type each one of them:
    • Dism /Online /Cleanup-Image /CheckHealth
    • Dism /Online /Cleanup-Image /ScanHealth
    • exe /Online /Cleanup-image /Restorehealth
  • Do not close the window if the process takes a while as it will probably take a few minutes to finish.

Option 4 – Try using the image from the official site of Microsoft

If none of the options given above worked, you can try to use the image from Microsoft’s official site. This would help, especially if the error is caused by a corrupted image or image folder with incomplete files.
Read More
How to Fix Can’t start your Camera, 0xa00f429f
If you are using the Camera app on your Windows 10 computer but encountered an error code 0xa00f429f with an error message that says, “Can’t start your camera”, read on as this post will guide you in fixing this problem. This kind of error in the Camera app could be due to a recent update gone wrong or it could also be due to a corrupted driver. If you are certain that the camera is connected and is properly installed, you can try to check for updated drivers. The error code signifies that the drivers have to be updated. However, that isn’t always the case sometimes as the problem could also have something to do with corruption in the driver. The effective ways to troubleshoot this problem would be trying to reinstall or reset the Windows Camera app, or update, rollback or uninstall some device drivers as well as use the Registry Editor. Before you proceed with the instructions provided below, make sure that you have admin privileges and don’t forget to create a System Restore point.

Option 1 – Try to reset or reinstall the Windows Camera app

As pointed out earlier, you can also reset the Camera app to fix the error. To do so, follow the steps below.
  • The first thing you have to do is go to the My Pictures folder under the C: drive of the File Explorer and then delete the Camera Roll folder.
  • Once you’re done, right-click on an empty area on your screen and create a new folder and name it “Camera Roll”.
  • Then from the Start menu open the Settings app and select System.
  • From there, navigate to the Apps and features section.
  • Now go to Camera and click on the Advanced Options and click the Reset button.

Option 2 – Try to reinstall the Camera app

If resetting the Camera app didn’t help, you might want to reinstall it by following these steps:
  • Tap the Win + X keys and select the “Windows PowerShell (Admin)” option from the menu to open Windows PowerShell as admin.
  • Next, type this command to uninstall the Camera app: Get-AppxPackage *camera* | Remove-AppxPackage
  • Once done, exit the Windows PowerShell and restart your computer and then try to install the latest version of the Camera app from Microsoft Store.

Option 3 – Try to rollback, update or disable drivers

The next thing you can do to fix the error code 0xa00f429f in the Camera app is to roll back, or update, or disable device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.
  • Open the Devices Manager from the Win X Menu.
  • After opening the Device Manager, look for the device drivers which have a yellow exclamation mark.
  • Then right-click on each one of them. If you haven’t updated this driver in a while, select the “Update Driver” option. On the other hand, if you’ve just updated this driver, then select the Uninstall Device option.
  • Next, follow the screen option to update or uninstall it.
  • Finally, restart your computer. It will just reinstall the device drivers automatically if you have chosen to uninstall them.
Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try to use the Registry Editor

  • Tap the Win + R keys to open the Run dialog box and type “Regedit” in the field and then hit Enter to open the Registry Editor.
  • Next, navigate to this registry key: ComputerHKEY_LOCAL_MACHINESOFTWAREWOW6432NodeMicrosoftWindows Media FoundationPlatform
  • From there, right-click on any empty space on the right side part of the window and select New > DWORD (32-bit) Value.
  • Then name it as “EnableFrameServerMode” and double click on it.
  • Now set its value data to “0” and its base value as Hexadecimal and then click on OK.
  • After that, restart your computer and see if it helped in fixing the problem or not.
Read More
Ordinal not found, dynamic link library Error
If you encounter an error message saying, “The ordinal xxx could not be located in the dynamic link library C:/Program Files (x86)/Microsoft VS Code Insiderscode – insiders.exe“ and you see a reference of a missing DLL file, then this indicates that the software is trying to locate the related DLL file, however, it is missing, hence the error. The error mentioned “Ordinal” which refers to the order of a number mathematically, e.g. 1st, 2nd, etc. And in this error message, the ordinal is referring to an Xth file of an XX.DLL file which is missing which is why you’re getting this kind of error. When you get this particular error, it means that your computer is missing the Microsoft Visual C++ Redistributable program. As per the error message, XXX is a number that in turn is the Ordinal. There is also another common error related to Ordinal which says, “The ordinal 12404 could not be located in the dynamic link library mfc90u.dl”. The error message could be referring to any DLL in the message. And since all these DLL files are part of the package, the error changes quite a bit as the Visual Studio looks for that DLL file. To fix this error, here are some suggestions that might be of help.

Option 1 – Try installing Microsoft Visual C++ Redistributable

As pointed out earlier, the error pops up when the Microsoft Visual C++ Redistributable program is missing on your computer. Thus, you need to download it from the official website of Microsoft. Once you’ve downloaded the Microsoft Visual C++ Feature Pack Redistributable Package, install it and then check if the error is now fixed.

Option 2 – Try to install OpenSSL

If you encounter the same error message but it points out that the LIBEAY32.DLL file is missing, then you have to install OpenSSL. In such a case, you will see the following error message:
“Ordinal not found. The Ordinal [Xxxx] could not be located in the Dynamic Link Library Libeay32.dll.”
 Make sure that when you install OpenSSL, you do it into the Windows system directory since the Libeay32.dll file is related to security.

Option 3 – Try to check Windows Updates

There are instances when Microsoft rolls out the framework and related updates via Windows Updates. It could be that an update related to DLL is still pending which is why you need to check Windows Updates. To do so, go to Settings > Update and Security and from there check if there is any pending update. If there is, you need to install that update and then restart your computer if needed.
Read More
How to Fix Drwtsn32.exe Application Error

What is Drwtsn32.exe Application Error?

Drwtsn32.exe (DrWatson Postmortem Debugger) is a process file from Microsoft Corporation that runs on Microsoft Windows Operating System. This file is digitally signed from Microsoft Windows Component Publisher- Microsoft Timestamping Service. This file is a type of executable file. It is useful to debug and creates log files when an error occurs during running or program execution. The information logged by DrWatson is used by technical support personnel to diagnose a program error for a computer running Windows. It creates log files in the following location C:Documents and SettingsAll UsersApplication DataMicrosoftDr Watson. However, when using Internet Explorer, MS Outlook or any other application on Windows, you can experience drwtsn32.exe application error. This error occurs when the drwtsn32.exe file crashes. The error is displayed as:
“DrWatson Postmortem Debugger has encountered a problem and needs to close” "drwtsn32.exe - DLL Initialization Failed" when shutting down

Solution

Restoro box imageError Causes

The ultimate reason behind ‘drwtsn32.exe application error’ is malware and viral infection. Malicious software can enter your PC through downloaded files , browsing on unsafe websites and phishing emails. These viruses can disguise themselves as DrWatson utility. Plus theymay have the same name as this process. However, the best way to detect if it is a virus is to track its location. Malicious software will usually hide in some other location instead of its standard location. However, other reasons for this error also include incompatible software and damaged system files.

Further Information and Manual Repair

a) Scan PC with an Anti-Virus

It is advisable to repair this issue right away especially if the underlying cause is a viral infection typically because viruses can expose you to privacy errors and risks such as cybercrime, identity theft, and data security issues. To resolve it, download a powerful antivirus. Scan your PC with it and remove all the viruses immediately. However, when doing so, you may have to compromise PC performance and halt other PC activities. Anti-viruses are notorious for slowing down PC speed. In addition to this, sometimes you may have to stop other activities on your PC for the antivirus to scan for viruses.

b) Repair Registry Errors with Restoro

Nonetheless, if the drwtsn32.exe application error is related to system file corruption, then this indicates registry issues where all the system data is stored. Registry issues occur if you don’t maintain your PC properly and let invalid, wasted and obsolete files accumulate on your PC. This damages and corrupts the system files and generates such error messages. To repair it, download a registry cleaner. However, the best alternative to resolve drwtsn32.exe application error in seconds whether the error is linked to registry issues or viral infection is to download Restoro. This is a multi functional PC fixer embedded with multiple utilities including a powerful antivirus, a registry cleaner and a system optimizer. It wipes out all the unnecessary files stored in the registry, repairs the damaged and corrupt system files and restores the registry. With the help of the antivirus, all privacy errors and viruses are scanned on your PC and removed immediately. And to ensure your system’s speed is not compromised, it also functions as a system optimizer and increases your PC’s speed significantly. The software is safe and efficient. It has simple navigations and a user-friendly interface which makes it very easy for all levels of users to work around. It is compatible with all Windows versions. Click here to download Restoro and resolve drwtsn32.exe application error today!
Read More
Shift Key is not working in Windows
A lot of users rely on keyboard shortcuts to carry out tasks on their PCs. One of the most common keyboard shortcuts used is the Ctrl + Shift + Esc which opens the Task Manager. As you can see, the Shift key is not just used to capitalize a text as it can also be used for other functions and plays an essential role in operating a computer. However, if you suddenly find it not working, read on as this post will help you fix the problem. If your Shift key is not working, there are several potential fixes you can check out to fix it. These are the different ways to get rid of the Shift key not working issue on Windows 10:
  1. Physically clean the key and keyboard
  2. Disable Sticky Keys.
  3. Update, Reinstall, or Rollback Keyboard driver.
  4. Test the keyboard on another system.
  5. Check your connections
  6. Run the Hardware troubleshooter
  7. Troubleshoot in Clean Boot State.

Option 1 – Clean the keyboard keys physically

Your keyboard might not be working properly due to some dirt or other corrosion. Thus, you need to clean your keyboard, especially the Shift key. First, you need to shut down your computer and then unplug the keyboard if you are using a desktop computer and then prepare it for cleaning. After that, use a small cotton ear cleaning tool to get between the creases and clean them. You can dip it slightly in alcohol to make it more efficient in cleaning dust and dirt. And if you can, you have the option to pull apart the keyboard completely and then wipe away all the corrosion from the inside. Once you’re done, put the keyboard back together and then plug it back into your PC. Now turn your PC on and check if the Shift key is now working.

Option 2 – Try to disable the Sticky keys

Another thing you can try is to disable the Stick keys. How? Refer to these steps:
  • Tap the Win + I keys to open the Settings app.
  • After that, navigate to the Ease of Access section, and here, select Keyboard.
  • Next, make sure that the option for Press one key at a time under the Sticky Keys is toggled off.

Option 3 – Reinstall, update or rollback your keyboard driver

Once you’ve determined that the problem is in the software part of the keyboard, it is now time to try to reinstall, update or roll back your keyboard drivers. To reinstall the driver for your keyboard, refer to these steps:
  • From the WinX Menu, open the Device Manager.
  • In the Device Manager, you should find your laptop’s keyboard under the “Keyboards” option. Right-click on it and select the “Uninstall” option.
Note: If you’re not quite certain about your laptop’s keyboard, you can uninstall all the keyboards if there’s more than one.
  • After that, restart your PC and see if the keyboard driver is installing automatically. If not, open the Device Manager again and right-click on Keyboards, and select the option “Scan for hardware changes” to install it.
Once the keyboard driver is installed again, check if your keyboard is now working properly or not.

Option 4 – Try connecting the keyboard to a different USB port or another computer

The problem might have something to do with the USB port that’s currently in use by your keyboard. It could be that it’s not working so it makes sense to unplug it and attach it to another USB port. You can also clean the USB port on both ends to ensure that they are not affected by corrosion. In addition, you can also try connecting the keyboard to a different computer and see if the Shift key works there or not.

Option 5 – Try to check your connections

You can also try checking if the connection mode you are using for your keyboard is functioning properly. For instance, if you are using a Surface 2-in-device, you can clean the connection pins and see if it resolves the problem.

Option 6 – Run the Hardware and Devices Troubleshooters

  • The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
  • After opening Settings, look for the Update and Security option and select it.
  • From there, go to the Troubleshoot option located on the left-hand side of the list.
  • Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
  • After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

Option 7 – Put your PC in a Clean Boot State

You might also want to put your computer in a Clean Boot State to fix the problem with the Shift key. It could be that there is a third-party program that’s preventing the Shift key from functioning. To isolate this possibility, you need to put your computer in a Clean Boot State.
  • Log onto your PC as an administrator.
  • Type in MSConfig in the Start Search to open the System Configuration utility.
  • From there, go to the General tab and click “Selective startup”.
  • Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
  • Next, click the Services tab and select the “Hide All Microsoft Services” check box.
  • Click Disable all.
  • Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
  • Now try to connect the external devices and check if the error is now gone.
Read More
Your computer has lost the lease to IP Address
If you encounter an error message that states, “Your computer has lost the lease to its IP Address <IP ADDRESS> on the Network Card with network address <NETWORK ADDRESS>”, then this post might be of help to you. This kind of error due to the timeout caused by the DHCPv6 address which is used to connect the client to the user network as an independent client or a part of a domain. There are a lot of potential fixes you can try to fix this error and we will be discussing each one of them below. You can try to reboot your router, flush the DNS cache, reset the Network adapter, toggle the DHCPv6 Lease time or disable IPv6 in the Network Center. For more details, refer to the following options.

Option 1 – Try rebooting your router

The first thing you can try to do to fix the error is to simply restart your router. All you need to do is reboot the router from its Admin panel or you can also turn it off manually and turn it back on after a couple of seconds so that it can completely reboot. Once you’re done, try accessing your server again and see if the error is now fixed.

Option 2 – Try to flush the DNS configuration

You could also try to flush the DNS configuration in your computer to fix the error. How? Refer to these steps:
  • Tap the Win + X key combination and click on the Command Prompt (Admin) option or you could also search “cmd” in the Cortana search box and right-click on Command Prompt from the search results and select the “Run as administrator” option.
  • After opening Command Prompt with admin privileges, enter each one of the commands given below sequentially in order to flush the DNS cache.
    • ipconfig/release
    • ipconfig/renew
    • ipconfig/flushdns
  • Now type the exit command to close Command Prompt and then restart your computer and see if the problem is fixed.
One the other hand, you could also try to reset Winsock as well as the TCP/IP. Once done, just exit the Command Prompt and check if that fixes your issue. You may want to reset Winsock & reset TCP/IP as well.

Option 3 – Try to toggle the DHCPv6 Lease time

  • First, you need to log in to the Admin panel of your router.
  • Next, navigate to the DHCPv6 settings inside it and look for a field for Lease Time.
  • After you’ve found it, increase the Lease Time value to something greater than what is already entered depending on your preference.
  • Now apply the configuration and reboot your router to apply the modified settings. Just remember that if things didn’t work out, you can just change back the Lease Time value to what it was before.

Option 4 – Try disabling the IPv6 in the Network Center

  • Tap the Win + X key combination and click on Network Connections.
  • This will open the Settings app on a specific page. Now on the right-side panel, click on the Network and Sharing Center link.
  • After that, it will open the Control Panel and from there, click on the network that your computer is connected to and then click on Properties.
  • Next, uncheck the entry that says, “Internet Protocol Version 6 (TCP/IPv6)” in the list that populates.
  • Now click on OK and close all other windows and see if the error is fixed.

Option 5 – Run the Network Adapter troubleshooter

To run the Network Troubleshooter, refer to these steps:
  • Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
  • Next, scroll down and select the “Network Adapter” option from the right pane.
  • Then click on the Run Troubleshooter” button.
  • After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
  • Restart your computer.

Option 6 – Try to perform Network Reset

You can also try to perform a Network Reset to resolve the problem. This will reset the entire network configuration including your IP address. To perform Network Reset, follow these steps:
  • Tap the Win + I keys to open Settings.
  • From there, go to the Network and Internet section.
  • Next, scroll down and look for “Network Reset” under the status pane.
  • After that, click on Network Reset and then on Reset now to start resetting the network configuration. Once done, check if it is able to fix the error or not.
Read More
How to Fix Windows 10 Error 0x80070426

Error Code0x80070426 - What is it?

When Windows evolved into Windows 10, the program known as Windows Security Essentials is no longer. It is now the program known as Windows Defender. When a computer is upgraded from a previous version of Windows up to Windows 10, the Windows Defender takes over and will replace the Security Essentials. In a small percentage of Windows 10 upgrades, something will go wrong and the new program will fail to replace Security Essentials. The result will be that the operating system has both of the programs installed. In this case, Windows Defender will not offer any protection and Security Essentials will not be able to defend either. This error code will also present itself when the Windows Mail App in Windows 10 fail to retrieve and sync email from the user's account.

Common symptoms include:

  • There will be an error message that says: “An error has occurred in the program initialization. If this problem does continue, contact your System Admin. Error code 0x80070426.”
  • The computer will be left completely vulnerable to spyware and viruses.
  • The Windows Mail App will not be able to retrieve mail and will not sync with the PC user's mail.
  • The user can be doing anything on their computer and the error code will show up unprompted.
  • The computer will lock up, become slow, crash, or even freeze when dealing with error code 0x80070426.
  • The programs from an older version of Windows do not replace the newer version from Windows 10.

Solution

Restoro box imageError Causes

Error code 0x80070426 will present itself when a PC user has upgraded their OS from a previous version of Windows to the new Windows 10 version. When this happens, a small portion of users will experience the disconnect between older versions of specific programs, namely the virus protection. When the previous version of the program under a different name is not completely removed and the new virus protection program is installed, the programs will cancel each other out and collectively offer no protection.

This error code may also be found when Windows 10 tries to sync the user's email with the Windows Mail App.

Further Information and Manual Repair

There are a few methods to repair this problem. It should be noted that should anyone feel that the instructions are too complicated, they should contact a Windows repair technician to ensure that the error is fixed properly.

Method One: Uninstall Microsoft Essentials

Hold down the Windows Key and press R. Type in taskmgr into the run dialogue. You should locate the Windows Defender Service (this may show up as Windefend). Right-click on it and then choose Stop.

This will stop the program, but the program will start back up automatically when the computer restarts. While this program is stopped, uninstall Essentials.

To do this: go to Control Panel, Programs, and Features, Uninstall a Program. Alternately, you may hold down the Windows Key and press R, type in appwiz.cpl, click OK, and then locate Microsoft Essentials. Uninstall it, and then restart your computer.

After this is done, go to Settings, Update, and Security. Choose Windows Defender and ensure that Real-time protection is on. Refer back to the Task Manager, Services. Make sure that Defender service is on and running.

Method Two: If the problem occurs in the Windows Mail App

When error code 0x80070426 presents itself in the form of an error with the Mail app, it may be necessary to run an SFC scan.

Right-click on the Start menu or Windows icon, and select Command prompt. The command prompt may be navigated by using shortcut keys Win and X and then select it.

Run the command prompt and then type in sfc /scannow and then press enter. The SFC scan will be run, and be careful not to abort the process before it has finished. This will scan for any files that are lost or corrupt on the PC.

If the scan has found any corrupt files, type in this code and then hit Enter: findstr /c:”[SR]” %windir%LogsCBSCBS.log >”%userprofile%Desktopsfcdetails.txt.

To skip the repair of corrupt or missing files, type in: Dism /Online /Cleanup-Image /RestoreHealth. The details of the scan can be found on the sfcdetails.txt file that will be on the desktop.

Method Three: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.
Read More
How to Fix Remote Computer requires network level authentication Error in Windows 10
A couple of Windows 10 users have reported an error on domain-connected systems when they tried accessing their computer systems remotely. This occurs when the network level authentication or NLA is enabled on the computer. If you are one of these users, you better keep reading as this post will guide you on how you can fix this error. To resolve this issue, there are several workarounds you can try. You can either disable this option directly via properties or you can also modify some registry entries or sub-keys and restart the system. When you encounter this problem, an error message pops up that states:
“The remote computer that you are trying to connect to requires network level authentication (NLA), but your windows domain controller cannot be contacted to perform NLA. If you are an administrator on the remote computer, you can disable NLA by using the options on the Remote tab of the System Properties dialog box.”
Or you could also see this error message instead:
“The remote computer requires Network Level Authentication, which your computer does not support. For assistance, contact your system administrator or technical support.”
Before you proceed in troubleshooting the problem using the options provided below, you need to create a backup for your data or system restore point as well as make a copy of any registry entries you are going to modify.

Option 1 – Disable Network Level Authentication via Properties

The NLA is a useful tool that provides your computer with extra security and helps network administrators in controlling who can log into the system with just a click of a single box. However, there are times when it can become a disadvantage and could prevent you from accessing your system remotely. Thus, you need to disable it using Properties.
  • Tap the Win + R keys to open the Run dialog box.
  • After that, type in “sysdm.cpl” and tap Enter to open System Properties.
  • Next, go to the remote tab and uncheck the checkbox for the “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)” option.
  • Now click the Apply button to save the changes made and exit System Properties and then try logging into the remote computer again and see if the problem is fixed or not.

Option 2 – Disable NLA via Registry Editor

Note that you can only use this option if the first one didn’t work for you. Take note that this option will require you to restart your PC completely which could mean some downtime if your computer is running a production server. So make sure to save all your work.
  • Tap the Win + R keys to open the Run dialog box and then type in “Regedit” in the field and tap Enter to open the Registry Editor.
  • From there, click on File > Connect Network Registry and input the details of the remote computer and then try to connect.
  • Navigate to the path below after you’re connected:
HKLM >SYSTEM > CurrentControlSet > Control >Terminal Server > WinStations > RDP-Tcp
  • After that, change the values given below to “0”
    • SecurityLayer
    • UserAuthentication
  • The navigate to PowerShell and execute this command – restart-computer

Option 3 – Disable NLA via PowerShell

PowerShell allows you to tap into the remote computer and once you’ve targeted the machine, you can execute the commands given below to disable NLA.
  • Tap the Win + S to open Search and then type in “PowerShell” in the field. Right-click on the related result and select the “Run as administrator” option.
  • After opening PowerShell, execute the command below:
  1. Once in the PowerShell, execute the following command:
$TargetMachine = “Target-Machine-Name” (Get-WmiObject -class “Win32_TSGeneralSetting” -Namespace rootcimv2terminalservices -ComputerName $TargetMachine -Filter “TerminalName=’RDP-tcp'”).SetUserAuthenticationRequired(0) Note: In the command given, the “Target-Machine-Name” is the name of the machine you are targeting.

Option 4 – Use the Group Policy Editor to disable NLA

Another option you can use to disable NLA is via the Group Policy Editor. This is ideal for you if you are blanket disabling. Just take note that the Group Policy Editor is a powerful tool and that if you make some mistakes by changing values you have no clue about, you can render your computer useless so make sure that you create a backup for all the values before you proceed.
  • Tap the Win + R keys to open the Run dialog box.
  • Then type in “gpedit.msc” and tap Enter to open the Group Policy Editor.
  • From there, go to this path – Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
  • After that, search for “Require user authentication for remote connections by using Network Level Authentication” and set it to disabled.
  • Now check if the error is fixed or not.
Read More
How to Fix The Rtl70.bpl Error on Your System

Rtl70.bpl Error - What is it?

To understand Rt170.bpl error code, it is important to have a good understanding of .bpl files first. BPL is the abbreviation of Borland Package Library. BPL is a developer file format used by Borland. It contains dynamic link libraries which are used for constructing Borland programs. BPL files are most commonly used for Borland Delphi programs. Delphi competes with Visual Basic as an offering for an object-oriented visual programming approach to application development. There are many programs/applications on your system that use rtl70.bpl file format to run successfully on Windows PC. The rtl70.bpl error occurs when this file gets damaged or corrupted. It fails to execute the command and run the application on your system. When your computer experiences this problem with this file, the following error messages are likely to appear:
  • rtl70.bpl is not responding
  • Runtime error: rtl70.bpl
  • Symantec User Session has encountered a problem and needs to close. We are sorry for the inconvenience. Application Name: rtl70.bpl
This error code exposes you to system freeze, crash, abrupt system shutdowns, blue screen of death errors, and it also reduces your PC performance.

Solution

Restoro box imageError Causes

The potential causes of rtl70.bpl error code includes:
  • DLL file was damaged due to viral infection or spyware
  • DLL file was overwritten by an incompatible version
  • Poor program installation
  • Too many invalid and obsolete registry entries stored in the RAM
  • Related Registry entries are corrupt

Further Information and Manual Repair

Here are some of the best yet simple solutions for you to resolve rtl70.bpl error on your PC:

1. Reboot Your PC

Sometimes this error can be resolved by simply restarting your system. Try rebooting your system and running .bpl supported program. If the program runs after you reboot your PC, then that’s great! But you should keep in mind that this is a temporary solution. The error may reappear anytime soon. So, it is advisable to consider a long-term solution for repairing the error code for the longest time.

2. Uninstall and then Reinstall the Program Causing the Error

If the error occurred after a certain program installed on your system,  it is advisable to uninstall it and then reinstall the program. Simply go to the control panel, select Add/Remove program option and uninstall the program that you recently installed that could be triggering the rtl70.bpl error code. Now reinstall and run it on your system. If the error is resolved, then this means the poor installation was the cause. If not, then this means the cause of the error is related to the registry.

3. Registry Restore to Fix rt170.bpl error

There are two ways to go about it. The first one is to click on the start menu, type registry editor, and press run. This will open the registry editor. Now click on the computer option then click file and import. This helps restore the registry but it is possible that the problem might persist. The error code may pop up again. Also, if the registry is damaged due to viral infection, then this solution may not work and you may still experience the error on your system. Then you will also have to download an antivirus which may further reduce the speed of your PC. However, the best way to restore the registry and to get rid of the error code for the longest time is to download Restoro. This is a new, user-friendly, high and multi-functional repair tool that functions as a registry cleaner and a system optimizer. It cleans the registry by scanning and removing all the unnecessary and obsolete files saved in RAM such as junk files, internet history, invalid registry entries, and more. It also repairs the damaged dll files and restores the registry thereby resolving the rtl70.bpl error. Restoro is easy to use, safe, efficient, and compatible on all Windows versions. To get started and resolve the rtl70.bpl error code in just a few seconds on your system click here and download Restoro.
Read More
Fix Failed to transfer logged messages ...
One of the most common hardware issues with any PC usually has something to do with the hard drive so if your hard drive experiences some errors, you could end up losing a lot of important information that’s stored in your computer. This is why Windows provided users with the CHKDSK utility which helps in looking for bad sectors on the drive. However, there are times when the CHKDSK utility could also face issues like the following error:
“Failed to transfer logged messages to the log event with status 50.”
According to security experts, this error is most likely due to the hard drive or RAM being in a “Read-only” state. It could also be due to some physical issues with the hard drive. On the other hand, it could be that the system is prevented from creating logs by some drive, service, or malware. To fix this error, you have to check if the hard disk is writable. You could also try to run the CHKDSK utility in Safe Mode or you could also check the physical status of your hard disk or external drive.

Option 1 – Check if the hard disk is writable

Although the CHKDSK utility checks for bad sectors in the hard drive, it also has to create logs of the result. And as states in the error message, the CHKDSK utility is not able to log the logged messages. This kind of error occurs when the log can’t be written to an installation disk. You can find the log in this location, “C:WindowsSystem32LogfilesSrtSrtTrail.txt”. Now you have to check if the drive writable by following these steps:
  • Log in as administrator and right-click on the system drive.
  • Select Properties and then go to the Security tab. Here, check if you are allowed to modify the drive. If not, click on Edit (as an administrator).
  • Now edit the permissions for the SYSTEM and Administrators group. Note that these are the only default settings for these two groups or usernames.
  • Then click on the Apply button save the changes made and exit.

Option 2 – Run the CHKDSK utility in Safe Mode

You could also try to run the CHKDSK utility in Safe Mode as this might solve the error.
  • Boot your computer in Safe Mode.
  • Next, open Command Prompt with admin privileges.
  • Then type and enter this command to execute it: chkdsk c: /f /r
  • Wait until the process is completed and boot your computer normally and then run the CHKDSK utility again and check if the “Failed to transfer logged messages to the log event with status 50” error is now fixed.

Option 3 – Try to check the hard disk or external drive physically

If the first two options didn’t work, you might want to check the physical status of your hard disk or external drive as the problem could root from there. You can try to tighten the wires that connect the hard disk to the motherboard. However, if it doesn’t help, you should seek out assistance from a hardware technician.
Read More
1 2 3 171
Logo
Copyright © 2023, ErrorTools. All Rights Reserved
Trademark: Microsoft Windows logos are registered trademarks of Microsoft. Disclaimer: ErrorTools.com is not affiliated with Microsoft, nor claims direct affiliation.
The information on this page is provided for information purposes only.
DMCA.com Protection Status