Steam Deck, a modern PC handheld console

If you are trying to connect to the internet using a Wi-Fi, Ethernet, or a Wi-Fi connection and you suddenly encounter Error 633, then read on as this post will guide you on how you can fix this problem in your Windows 10 computer. According to users who encountered the same problem, when they try to connect to the internet, an error pops up that states, “The modem or other connecting device is either already in use or not appropriately configured”. This error is the VPN Error 633 which indicates that the modem is malfunctioning due to some broken configuration. It is possible that this broken configuration is caused by the WAN Miniport device which is associated with your preferred VPN protocol. It could also be due to the TCP port that’s required for the VPN connection to work might be used by another application. There are instances when Error 622 could occur when there are multiple internet connections set up on one device or when the communication port is exploited by another program. It could also occur when the affected modem is not bound to one specific device. Thus, any model and computer can be affected by this problem. The first and basic thing you can do to fix the VPN Error 633 is to turn off or unplug the modem your computer is using and then plug it back in to see if the problem is fixed. If not, then there are several other potential fixes you need to check out to resolve the problem. You can try the suggestions provided below and see if any of them help.

Option 1 – Run the Network Adapter Troubleshooter

• 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.

Option 2 – Try to explicitly reserve the TCP port

The next thing you can do to fix the error is to reserve the TCP port explicitly and to do that, follow the steps below.

• Tap the Win + R keys to pull up the Run dialog box and type “Regedit” in the field and hit Enter to open the Registry Editor.
• Next, navigate to this registry path: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters
• After that, follow the path New > Multi-String Value on the edit menu and rename the multi-string value as “ReservedPorts” and then double click on it.
• Now in the value data of ReservedPorts, input “1723-1723” and click OK to save the changes made.
• Close the Registry Editor and restart your PC. Once your computer has restarted, check if the VPN Error 633 is fixed or not.

Option 3 – Try to use the netstat command

• In the Windows Start Search, type “cmd” and from the search results that appear, right-click on Command Prompt and then select the “Run as administrator” option.
• After opening Command Prompt as admin, type this command and hit Enter: netstat –aon
• After that, the output will be displayed and from there, look for the process ID or PID of any program that uses the TCP port 1723 on your computer.
• Next, type this next command and hit Enter: taskkill /PID PID /F
• Once the command has been executed, the concerned program will be forced to close and the TCP port 1723 will be freed up. Keep in mind that the taskkill command ends the process corresponds to the process ID number and the given command above, “/F” option is used to end the program’s process forcefully.
• Now restart your computer and after that, the concerned program should start using a TCP port other than 1723 which leaves the TCP port 1723 free for your internet device to use.

Option 4 – Remove any irrelevant internet device programs

You could also try removing any irrelevant device programs since it is possible that any of these programs could be the one that’s causing the modem to malfunction. These irrelevant programs could be an internet booster or third-party tools that comes with the modem and so on. These programs are not necessarily needed for your modem to function. Thus, if you want to fix the VPN Error 633, you can try uninstalling them and see if it fixed the error.

Option 5 – Update the Network Adapter drivers

You might also want to update the Network Adapter drivers by following these steps:

• Tap the Win + R keys to launch the Run window and then type in the “devmgmt.msc” command and hit Enter to open the Device Manager window.
• Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand them.
• Then right-click on each one of the Network drivers and update them all.
• Restart your PC and see if it helped in fixing the BSOD error.

Note: If updating the network drivers didn’t help in fixing the VPN Error 633, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly. To reinstall the network adapter driver, refer to these steps:

• Open the Devices Manager from the Win X Menu.
• Then locate the device drivers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Experiencing issues while using Remote Desktop connections is not uncommon. One of the issues that users encountered recently while trying to connect to their Remote Desktop network is the error saying, “Your credentials did not work, The login attempt failed”. If you are one of these users, then you’ve come to the right place as this post will walk you through fixing the problem. When facing this kind of problem, the first thing you can try before you do some troubleshooting steps is to verify the credentials. But if you are certain that you’ve entered the correct credentials just like what other users reported, then it’s completely a different matter. Based on the reports, this error is common on newly installed versions of Windows 10 or after reinstalling the operating system which could mean that the problem might be due to the Windows security policies or the username might have been recently modified. The latter case is a possibility especially if you’ve reinstalled Windows 10 and had entered a new username. In such a case, you will really have a difficult time connecting to your Remote Desktop connection since its credentials do not really automatically change. If you’ve verified that your credentials are correct, then now’s the time you troubleshoot the problem with the help of the potential fixes provided below. Just make sure that you follow each one of them in sequence.

Option 1 –Try to 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 2 – Try to change the network profile from public to private

According to some reports, this error occurs on systems where the network profile was set to public. Thus, you need to change the network profile to private to resolve the problem. How? Refer to these steps:

• Go to Start and from there click on Settings > Network & Internet > Status.
• Next, click on the “Change connection properties” option.
• After that, set the radio button of Network Profile from Public to Private.
• Wait for a couple of seconds until the system is done applying the changes you’ve made and then see if you can now connect to the Remote Desktop connection.

Option 3 – Try changing the account username

As mentioned, one of the possible causes for this error is the reinstallation of the operating system. You might have changed the username for the system but it does not really change the username of the Remote Desktop connection as well. Thus, you have to change the username back to what it was before you’ve reinstalled Windows 10.

Option 4 – Try modifying the Windows Security Policy

You can also try to edit the Windows Security Policy as it could help in resolving the error. This Windows Security Policy, when enabled, will not allow non-admin users to log on to the Remote Desktop connection. So if you want to allow non-admin users to use the Remote Desktop connection, then you need to modify this policy. Note that you can only do that if you are the admin of the system yourself.

• Tap the Win + R keys to open the Run utility.
• Then type “secpol.msc” in the field and tap Enter or click OK to open the Local Security Policy.
• After opening the Local Security Policy window, select Local Policies > User Rights Agreement located on the left pane.
• Next, double click on “Allow log on through Remote Desktop Services” located in the right pane.
• And in the next window that appears, select Add user or group.
• After that, type in the username of the intended non-admin user under the “Enter the object names to select” column.
• Once done, click on the Check Names button to fix the username and then click OK to save the changes made.
• Restart your computer.

Option 5 – Use the Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” in the field and tap Enter to open the Group Policy Editor.
• Next, navigate to this path: Computer Configuration > Administrative Templates > System > Credentials Delegation.
• Double click on the “Allow delegating default credentials with NTLM-only server authentication” policy setting located on the right pane to edit it.
• After that, shift its radio button to Enabled and click on Show.
• Then type “TERMSRV/*” in the Value box and click OK.
• Now repeat the same for the following policy settings:
  • “Allow delegating default credentials”
  • “Allow delegating saved credentials”
  • “Allow delegating saved credentials with NTLM-only server authentication”

• Once you’re done, restart your computer and see if the problem is fixed.

Microsoft office has set itself as one of the most used and best suites for business use and MS Word as the most widely used word processor. But how even best are not immune to some small bugs and unexpected behaviors so is not Word. Word has stopped working is probably know to a wide audience of its users, I think I could safely say that each Word user has experienced this error at least once, luckily the error is not anything to worry about since it is an easily fixable issue.

Try automated solutions

There are some fully automated solutions that could fix any PC issues, some are available in free versions. If you prefer to do things manually however keep on reading and follow the instructions below.

Manual FIXES:

1. Update MS Word

   Make sure that you are running the latest build of Word in order to eliminate all bugs and to have a smooth running experience. Go to File > Account > Product Information > Update Options and click Enable Update and then select Update Now.

2. Check the file

   Corrupted files can cause this crash and this error, try opening another text file inside the Word to eliminate file corruption.

3. Run Word in safe mode and disable add-ins

   Did you know that MS Word has a safe mode like Windows? In this safe mode, Word will boot up just the application without any add-ins installed and in this environment, you can start one add-in by one to see which one is causing the issue. Press ⊞ WINDOWS + R to open the run dialog Inside run dialog type in winword /safe followed by ENTER to run Word in safe mode If MS Word works fine in Safe mode, disable all COM Add-ins (while being in safe mode) and restart Word. Re-enable the add-ins one at a time to identify the problematic one. Click on File and then on Options Click on Add-Ins from the options list Select COM Add-ins from the drop-down menu and click on Go Uncheck all the add-ins and click OK to confirm Close the Dialog Box and MS Word. Now try running MS Word normally and see if it works Repeat steps to enable the add-ins, one at a time, and check which add-in is causing this error

4. Repair Word installation

   Press ⊞ WINDOWS + R to open the run dialog In run dialog type in control panel and press ENTER Inside Control Panel click on Programs and Features Locate and click on Microsoft Office to select it Once selected click on change located on top of the application list Once Office Windows loads click on Repair Wait for the process to finish

5. Reinstall MS office

   If all the previous solutions failed next step would be to completely uninstall MS Office and install it again once the old one has been completely removed from the system. Go to the control panel as explained in the previous step and select Office Instead of Change this time click on uninstall and follow on-screen instructions Once uninstall is finished, install a new copy of MS Office.

Hello and welcome to our user account notifications in Windows 10 tutorial where we will dive a little more into how you can control notification and behavior settings for your or someone else's user account in your Windows 10. If you are annoyed with confirmation windows each time you start a new application or install one please keep reading and I am sure you will find just the right setting for you. User account options are a little hidden and not so obvious, well at least not in Windows 10 compared to previous Windows versions. Since we will not be able to find them under typical and standard settings we will need to do few tricks in order to get to them.

Opening control panel

First thing is to press ⊞ WINDOWS + R on your keyboard so the run dialog window pops up on your desktop. Once run dialog is shown type in it control panel as shown in the picture and press OK If you have followed the steps precisely, you should be now in the control panel of Windows 10. Click on the top-right view and choose large icons. The Control panel will switch to a grid-like view, in the current view go to the far-right and almost bottom icon where it says User Accounts and click on it.

User account settings

Once the user account opens click on the bottom link which says Change User Account Control settings. Please note that you will need to be logged in as an administrator or have administrator privileges in order to change this setting. Once you click on the link you will be presented with a User account control slider on the left and a brief explanation on the right Here in the picture, we see Windows default setting and an explanation of when and how he will notify you. If you wish to turn all notifications linked to programs changing computer or you making windows changes, click on the left slider and bring it all the way to the bottom where it says never notify me. If you prefer some notifications try to find which of the remaining 3 settings best suit your needs. Once you are done and satisfied with your choice click on OK.

In Windows 11 by default inside the Start menu, there is recommended section that contains recently opened folders, documents, and files. If you do not wish this section and do not want recent items in your Start menu there is an easy way to turn it off.

1. Press ⊞ WINDOWS + I to open settings
2. Click on Personalization
3. On the right side scroll down and click on Start
4. Click on the switch beside Show recently opened items in Start, Jump lists, and File Explorer
5. Close settings

Settings will be automatically applied and there will be no more recommended items inside your Start menu to create clutter, it will be nice and clean.

A lot of things can go wrong even when you’re only doing some simple operations or tasks on your computer and this is due to the fact that there are various small operations make up in order to perform the larger operations on your computer. So if any of these smaller operations are not properly working, it crashes the operation as a whole and it throws an error code instead. And one of these error codes is Error 0x800701e3. This particular error pops up when an error has occurred in the File Explorer when a transfer is initiated from one disk to another in your Windows 10 computer. When you encounter this error, you will get the following error message:

“Error 0x800701e3: The request failed due to a fatal hardware error.”

There are several methods you can check out to fix this error – you can try to run System Restore or Check Disk or format the destination drive or check the SMART attribute of the drive. For more details, refer to each one of the following options.

Option 1 – Try to run System Restore

Error 0x800701e3 might be due to some adjustments you’ve made in your computer’s settings. Thus, to fix this error, you can try undoing those changes using System Restore. How? Refer to these steps:

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and then check if your mouse is now back to its normal state.

Option 2 – Try running the Check Disk utility

You can also run the Check Disk utility in fixing Error 0x800701e3.

• In the Windows Search box, type “command prompt” and from the search results, right-click on Command Prompt and select “Run as administrator”.
• After opening Command Prompt, type this command and tap Enter: chkdsk <Partition Letter>: /f /r /x /b
• The command you entered will start to check for errors and fix them automatically. Else, it will throw an error message saying, “Chkdsk cannot run because the volume is in use by another process. Would you like the schedule this volume to be checked the next time the system restarts? (Y/N)”.
• Tap the Y key to schedule Disk Check the next time your computer restarts.

Option 3 – Try to format the destination drive

Formatting the destination drive could also help you resolve error 0x800701e3. To format your drive, follow these steps:

• First, open File Explorer and then right-click on the drive where you encountered the error.
• Next, select Format from the context menu. This will open a new mini window.
• Then select the NTFS option from the drop-down menu for the File System menu.
• After that, check the box labeled as Quick Format.
• Now click on Start. Keep in mind that doing so will remove all the contents of your storage device.

Option 4 – Verify the hard drive using SMART attributes

In case you don’t know, Windows has a built-in feature of SMART analysis which analyzes the hard drive/SSD and checks all the parameters by performing some minor operations. To use it, follow these steps:

• Tap the Win + S keys and type “command prompt” in the field then right-click on the related search result and select the “Run as administrator” option.
• After opening Command Prompt as admin, type the “wmic diskdrive get status” command and hit Enter.
• You should get a result after that, and if you see that it’s “normal”, proceed to the next option below

Sticky Notes is one of the useful programs and in the early days, the option is available for users to change the font size of the text a lot easier. However, for some unknown reason, Microsoft decided to get rid of this feature in the latest Windows Update. One would expect that the feature will be replaced by an even more useful feature but it’s not which makes the Sticky Notes app worse than before. Worry not though for it doesn’t have to stay that way as there is another thing you can try to change the font size in your Sticky Notes app and that’s what we’re going to cover in this post. As mentioned, Microsoft removing this font feature is quite strange and in the past, users asked for this feature and since it’s no longer available, you can try following the steps given below to bring it back. And for that, you need to go to the Ease of Access section in the Settings app. Refer to the steps given below for more instructions. Step 1: First, tap the Win + I keys to open Settings and then go to the Ease of Access section. Step 2: After going to the Ease of Access menu and select Display from the list of options. Step 3: From there, you should see an option that says “Make text bigger”. And then use your mouse to navigate to the slider to change the size of the font. Note: Take note that after doing all the steps above, it will change not just the Sticky Notes app but also everything in Windows 10. This method is actually the best since it only changes the size of the apps rather than a wholesale change in your Windows 10 computer. Step 4: Next, scroll under Display until you see the “Change the size of apps and text on the main display” option where you’ll see that the option is 100% but you’ll want to change that to 125%. Step 5: After that, click on the drop-down menu and select 125% and then restart your Windows 10 computer. Step 6: Now open the Sticky Notes app and check if you can now change the font size in the Sticky Notes app.

There are instances when the Windows 10 installation needs interaction before it reaches the file process. And so if you suddenly encounter the Windows Update Installation Failure 0x80240020 error under the Windows Update History, then you need to get it fixed. When you encounter this kind of Windows Update Error, you will see an error message that says, “The operation did not complete because there is no logged-on interactive user”. This error also indicates the “WU_E_NO_INTERACTIVE_USER” code. To resolve this issue, in this post we’ll walk you through a couple of steps but before you get started, know that you don’t have to run any troubleshooter or delete any file just to fix this error since all you have to do is enable one option that can automatically login with your account and complete the installation for you. With that said, just make sure to only try running Windows Update once you’re told to do so. There are two ways you can enable the option that could resolve the Windows Update Installation Failure 0x80240020 error. One is via Settings while the second one is via Registry Editor.

Option 1 – via Settings

Step 1: Go to Settings > Accounts > Sign-in Options. Step 2: From there, toggle on the “Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart” option. Step 3: After that, it will make sure that the interaction part is removed from the Windows Update process. Note: If your device is joined in a domain or if some work or email policies are applied to your device by your company or organization, then you wouldn’t be able to see this option in Settings and that’s where the Registry Editor comes in. Just make sure that you’re logged in as an administrator and that you create a System Restore Point first since registry hacks are sensitive and could highly impact how your computer behaves or functions. Once you have that covered, follow the steps below.

Option 2 – via Registry Editor

Step 1: In the Start search, type “Regedit” and hit Enter to open the Registry Editor. Step 2: Navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionWindowsUpdateOSUpgrade

Note: If the above-given registry key does not exist, you can simply create it. All you have to do is right-click on the WindowsUpdate key and then select the New Key option and type “OSUpgrade” as its name. Afterward, create a new DWORD (32-bit) Value and name it “AllowOSUpgrade” and set its value to 0x00000001. Step 3: Restart your computer and check if the error is now fixed. And then try to update your Windows 10 computer again and while you’re at it, make sure that you’re around your computer to interact with the prompts needed to complete the installation process.

USB Kill, a USB device is able to fry and damage your computer, mobile phone, router, etc. This device is quite dangerous and can kill electronics the moment it is inserted into an available port. By now people should know that they should not put unknown USB sticks into their devices because of potential virus and malware threats but this raises using unknown sticks to a whole new level.

Kill kits are not really new to the market, they have existed before but lately, technology really progressed and the latest USB sticks are really good, their success rate is around 95% which is pretty high and should not be taken lightly.

The second thing that you really should not play with strange USB sticks is that they dropped in price really hard, although top Kill kits will still go as high as around 300 USD, there are really cheap ones lurking in Ali Express that are just 6 USD!!! that makes them affordable devices for the mass market.

The device is made to take energy and current from the port it is plugged in, multiply it and release its charge back into the device, successfully frying some components immediately. Some more professional Kill sticks can even fry devices even when the device itself is not powered and can be even started remotely.

The point of this article is to make you aware that you should not in any kind of circumstances use and plug-in USB sticks into your devices that you do not know where they come from, especially from the mail!!

In this post, we will discuss what the “ bootres.dll ” file is in the Windows 10 operating system and where it’s also located. In addition, you will also be guided on how you can replace or fix a corrupt bootres.dll file which may prevent you from booting to your Windows desktop and will display an error message instead saying, “Boot critical file resourcescustombootres.dll is corrupt”. There are times when this error might also boot your PC to the Automatic Repair screen. DLL files, also known as Dynamic Link Libraries are external parts of applications that run on Windows as well as other operating systems. Almost all applications are not complete in themselves and store code in different files so if there is a need for the code, the related file being called by a certain application is loaded into memory and used. If the software or the operating system is unable to find the concerned DLL file or if the DLL file ends up getting corrupted, you will most likely get an error message. In case you don’t know, the bootres.dll file is a critical system OS file, size 90KB, and can be found in the Windows folder. It is a part of the Boot Resource Library and portrays an important role in making sure that your PC boots properly. So if it ends up getting corrupted, your PC may fail to boot correctly and you’ll get an error message instead. To resolve this problem, here are some suggestions that might help. If your PC automatically boots to the Automatic Repair screen, you need to click on that option to run the Automatic Repair. If it doesn’t work, you have to boot into the Advanced Startup options to manually access and run the Automatic Repair. Once you’re in the Advanced Options, you will be able to:

• Run Automatic Repair
• Use System Restore
• Start Windows from an external device
• Access Command Prompt
• And use the System Image Recovery to restore Windows from a Factory image.

If the Automatic Repair fails to fix the problem, you may have to use System Restore or the Command Prompt to carry out further troubleshooting steps. Refer to the guide below to use these tools.

Option 1 – Try running the System File Checker in Safe Mode

Running the System File Checker is the safest way to fix DLL file missing or corrupted errors are thrown up by the Windows operating system as it could give you better results. System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files that might be causing the Machine Check Exception BSOD error. To run the SFC command, follow the steps given below.

• Boot your PC into Safe Mode.
• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

Option 2 – Try running the DISM tool to repair the System Image

To repair the System Image, you need to use the DISM or Deployment Imaging and Servicing Management tool. The DISM tool is another command-line tool in the Windows operating system that could help users fix various corrupted system files. To use it, follow these steps:

• Open the Command Prompt as admin.
• Then type in this command: Dism /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.

Note: The command you executed will check for Windows component store corruption and will restore its good health. The scan might take up to 15 minutes. Once it is done, you have to restart your computer.

Option 3 – Try to repair the MBR and rebuild BCD

To repair the MBR and rebuild BCD, follow these steps: The problem might boil down to the Master Boot Records since the previous case has already been isolated. There are times when the Master Boot Records can get corrupted and even though it is a serious issue, it can still be rectified by repairing the Master Boot Record.

• Tao the F8 key while booting the system to go into the Windows Recovery Menu.
• Next, click on Troubleshoot.
• Then click on the Advanced options to get into the Automatic Repair menu.
• After that, you have to use the bootrex.exe tool, so click on the command prompt and type in the following commands, one after the other:
• bootrec /RebuildBcd
• bootrec /fixMbr
• bootrec /fixboot
• Exit and then go ahead and restart your PC.

Option 4 – Try running the ChkDsk utility

One of the best options you must try is running chkdsk as it will check the disk for any errors and repair them automatically. To use it, follow these steps:

• Boot your PC to the Advanced Options menu and click on Command Prompt.
• Once you’ve opened an elevated Command Prompt, type in the following command and tap Enter to execute it:

chkdsk C: /f /x /r

Note: “C” is the drive root drive so it could be changed if you’re using a different one.

Option 5 – Try resetting your PC

Go to the Advanced Options > Troubleshoot > and select the Reset This PC option from the menu and then select Keep my files.