Easy Methods of Fixing Error 1706

When you get the error information, "The Software Can Not Begin Because MSVCR100.Dll Is Missing", what this implies is that the Computer will be lacking the  MS Visual C++ 2010 libraries. The malfunction is rather frequent throughout installations. It doesn't matter the number of times you try to reinstall the program. The malfunction can happen whether you've been utilizing your pc for many years, or it's really a recent one.

Solution

Error Causes

a) Missing MSVCR100.DLL: As the problem message indicates, you get this information mainly because MSVCR100.DLL is completely missing. b) Broken MSVCR100.DLL: When the msvcr100.dll is broken, you will also get the same error, suggesting the software won't start. The thing you need to understand is the fact that MSVCR100.DLL is playing an important role in the application referred to as MS Visual C++ 2010 Redistributable Package. Without the MS Visual C++ 2010 Redistributable Package, any software that you simply make an effort to install won't start. You could possibly complete installing it by pursuing proper installation procedures, and then end up getting the "The Software Can Not Begin Because MSVCR100.Dll Is Missing" error.

Further Information and Manual Repair

If you get the "The Software Can Not Begin Because MSVCR100.Dll Is Missing" error information on an effective setup of any software, you shouldn't worry. You can really repair the issue and commence your recently installed software without any more hassle. Start by checking whether you presently use 64-bit or 32-bit Windows. Visit the start button, in case you use Winxp. Type winver. On the window that appears, click Run, subsequently push enter. Head to Start, in case you use both Win7 or Vista. Subsequently, click on the search box and type “Computer”. Right-click windows and subsequently click on Properties. Under Windows Edition, you'll find whether your Windows is 64-bit or 32-bit. Search for the correct variation of MS Visual C++ 2010 Redistributable Package, as soon as you discover whether your Windows is 64-bit or 32-bit. Down load the x86 variant of MS Visual C++ Redistributable Package if your version is 32-bit and you must obtain the x64 variant of MS Visual C++, for those who own a-64-bit version of Windows Operating System. You must never obtain MS Visual C++ 2010 Redistributable Package from third-party websites. This is because Microsoft doesn't charge a cent for the files. The files are openly and easily available on Microsoft. These files come in many different variants. Consequently, select what's suitable for your own Computer with regards to the version of Windows which you operate.

• Never pick the edition of MS Visual C++ 2010 Redistributable Package that's not compatible or appropriate to your Windows Operating System.

Make use of the release date, when installing MS Visual C++ 2010 Redistributable Package. You might also look out for Service Pack 1 and obtain it for your Windows. Service Pack 1 only ensures that you simply obtain the latest edition. As soon as you end installing the most up-to-date version of MS Visual C++ 2010 Redistributable Package as demonstrated above, reboot your computer and you'll not have to worry about getting the annoying"The Software Can Not Begin Because MSVCR100.Dll Is Missing" error message anymore.

Hello everyone and welcome to another tutorial on errortools.com, Windows itself when it is installed has a general idea about certain file types and how to open them, for example, image files would be opened with application photos, web links with the edge, etc. So when we double click on the known file type, Windows will start the default application for that type and open the file in it. But what if we do not want to open files in applications Microsoft thinks we should? What if we want to open the website in firefox or images in photoshop, or whatever. Luckily we can easily change which application Windows uses for which file type. Click on ⊞ WINDOWS to open the start menu and choose settings. On the settings screen, choose Apps. When the Apps screen opens on the left click on Default apps. On right, you will get a list of Windows default applications for certain types of files. Click on any application you would like to change and choose from the drop-down list a new one. Click on it and you are done.

Code 39 - What is it?

Code 39 is a device driver error code that pops up when the Windows operating system cannot load the driver for the hardware you want to use.

This hampers your ability to use the hardware properly. The error code is almost always presented in the following format:

“Windows cannot load the device driver for this hardware. The driver may be corrupted or missing.” Code 39

Error Causes

A device driver is a software program that tells the operating system how to control a particular hardware device. Each hardware device has a different driver.

There are separate device drivers for printers, CD-ROM readers, and keyboards, to name a few.

Many device drivers are already built into the operating system. But sometimes you will need to install a new device driver when you want to use a new piece of hardware device that the operating system is not familiar with, or does not anticipate.

Regardless of whether or not the drivers are already integrated into the operating system, you may still experience code 39, typically because of the corrupted or outdated drivers.

Outdated and corrupted drivers cause hardware malfunction and failure, which trigger device driver error codes like code 39. Other causes include incorrect registry values.

Further Information and Manual Repair

Below are some of the easiest and most effective methods to resolve Device Manager error code 39 on your PC.

To follow and implement these methods, you don’t require any technical knowledge or expertise. Simply follow these instructions to fix the error right away.

Method 1 - Fix with a Simple Reboot

There is a possibility that the error code 39 is caused by some fluke within the Device Manager or your BIOS.

If that’s the reason, then a simple PC reboot can resolve the issue immediately. Therefore, before you try anything, it is advisable to restart your system.

If it works, then that is great, but if it doesn’t, then don’t worry, try other methods given below to fix this problem successfully.

Method 2 - Uninstall and Reinstall Drivers

If the error code 39 is generated due to faulty or outdated drivers, then simply uninstall and remove them and then reinstall new driver versions. There are two ways to remove faulty drivers.

Method One

• One is, to go to the start menu, click on Control Panel, and then Add/Remove Programs.
• Remove the program and the driver you think is causing problems. This will thoroughly remove all traces of the faulty driver.
• To reinstall, follow the same steps but this time install the new device driver version.

Method Two

• The other way is to go to the start menu, type Device Manager in the search bar, and then press enter to continue.
• In the Device Manager, find and locate the problematic device.
• After that, double-click the category of device that you wish to uninstall. Let’s say, Windows is unable to load the graphics card driver.
• This means you will have to click on the Display Adapter category in the Device Manager to uninstall the graphics card.
• After you have successfully uninstalled, Windows will prompt you to confirm device removal.
• Simply click OK to confirm and proceed. To activate the changes, restart your PC.
• To reinstall, go to the Device Manager, click on the Action tab and then select the option ‘Scan for Hardware Changes.’

This method, although effective in resolving error code 39,  can be time-consuming. To avoid the hassle and save time, try method 3.

Method 3 - Update Drivers Automatically with DRIVERFIX

If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Code 43 - What is it?

Code 43, Device Manager Error, is reported when Windows doesn’t recognize a hardware device such as the video card, USB, printer, or any other piece of external hardware attached to your PC.

The Device Manager stops the hardware if it reports some kind of unspecified problem. It is mostly displayed in the following format:

“Windows has stopped this device because it has reported problems. Code 43”

Solution

Error Causes

Code 43 can be triggered due to several reasons. However, 95% of the times it is related to the device driver problems such as:

• Missing Drivers
• Corrupted Drivers
• Outdated Drivers

Driver problems pop up when either new driver versions are available or drivers become damaged due to some underlying reasons like viral infections.

Other than driver problems, code 43 can also pop up when you install and remove the software. This can cause hardware conflict in the registry, altering driver communication.

Code 43 can hamper your ability to use your desired device smoothly.  Although Code 43 is not a fatal error code like Runtime and BSoD errors, it is still advisable to resolve it immediately to avoid inconvenience.

You can sometimes bypass error code 43 temporarily by a simple PC reboot but this will not fix the problem permanently. For a permanent fix, try the methods given below.

Further Information and Manual Repair

To help you repair code 43 permanently from your PC, below are some of the best, easy perform, and effective solutions. Simply follow the steps to get rid of code 43 from your PC.

Method 1 - Launch and Run the Troubleshoot Wizard

This is one way to find the exact nature of the problem that spurred error code 43 to pop up. To launch and run the Troubleshoot Wizard, here’s what you need to do:

• Go to the start menu
• Type Device Manager in the search bar and then press enter
• Click on Device Manager to run it on your system
• Now click on the ‘General Tab’
• After that press Trouble Shoot to launch the Troubleshooting Wizard

The Wizard will diagnose the problem and provide you a solution to resolve it, all you have to do from there is to follow the Wizard’s instructions

Method 2 - Check the Hardware Documentation

If for some reason Method 1 doesn’t work,  another solution would be to check the hardware documentation for more information about diagnosing the problem.

Method 3 - Uninstall Faulty Drivers

If the underlying reason for code 43 is related to driver problems, then the best way to resolve it is to uninstall faulty drivers and then reinstall new drivers. One of the many ways to uninstall drivers is:

• Click on the start button
• Type ‘sysdm.cpl’ in the search box and then press enter to continue
• In the System Properties dialog box open the Hardware tab
• Click Device Manager and then double click Device Type
• Now click on the problematic hardware device reporting code 43
• After that go to the Driver tab and click Uninstall to uninstall that driver completely
• Visit the manufacturer’s website and download the new driver version
• Install it on your system by extracting the .ZIP file

Method 4 - Update Drivers Automatically

Identifying and updating new driver versions manually can be both frustrating and time-consuming especially if you are in a rush and no computer whiz.

Also, after you update the drivers, you need to keep checking them time and again to ensure they don’t become outdated. You need to update them every time new versions are available which can be stressful.

To avoid this hassle by repairing code 43 permanently, download DriverFIX. This is an innovative and user-friendly device driver software program exclusively designed to resolve all kinds of driver problems.

Whether code 43 occurs on your PC due to missing or outdated drivers, DriverFIX can resolve the problem easily.

The intelligent programming system embedded in this software enables it to detect problematic and outdated drivers in seconds.

It matches new and compatible versions and updates the drivers immediately, automatically, and on a regular basis in just a few clicks. This resolves code 43 and also ensures that all your drivers remain up to date.

DriverFIX is compatible with all Windows versions.

Click here to download DriverFIX to repair and resolve code 43 right away.

You might be familiar with the Encryption File System or EFS algorithm if you rather keep your files and folders encrypted. Encryption File System is a built-in feature in Windows 10 which allows users to secure their important files. Although there is an alternative way for you to secure your data on your Windows 10 computer, you can’t ignore the fact that the main advantage of an Encryption File System over BitLocker is that the former can help you encrypt a particular folder rather than encrypting the whole hard drive partition. If you move a file inside a folder encrypted with the Encrypting File System it will automatically get encrypted. There are some users who like this feature but unsurprisingly, there are some that don’t. So if whether you want your files encrypted when you place them in an encrypted folder or if you want to keep it as it is, read on as to how you can do it either way. You can enable or disable automatic encryption of files moved to encrypted folders in Windows 10 using the Registry Editor or the Group Policy Editor. Before you proceed, make sure to create a System Restore Point first because the modifications you’re about to make in your computer might affect its overall functioning so if anything goes wrong, you can always undo the changes. Once you have that covered, refer to the options given below to enable or disable automatic encryption in Windows 10.

Option 1 – Enable or disable automatic encryption using Registry Editor

• Press the Win key + R key at the same time to open the Run dialog box.
• Then type “Regedit” in the field and press Enter to open the Registry Editor and if a User Account Control or UAC prompt appears, just click Yes to proceed.
• After opening the Registry Editor, navigate to this key location: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer
• Next, right-click on Explorer and select New > DWORD (32-bit) Value and then name the newly create DWORD to “NoEncryptOnMove” and press Enter to save it.
• After that, double click on the NoEncryptOnMove DWORD and set its value to the following preferences:
  • 1 – Disable Auto Encryption of files moved to encrypted folders.
  • 0 – Enable Auto Encryption of files moved to encrypted folders.

• Now close the Registry Editor and restart your computer to successfully apply the changes made.

Option 2 – Enable or disable automatic encryption using the Group Policy Editor

• Press the Win + R keys to open the Run box and type “gpedit.msc” in the field and press Enter to open the Group Policy Editor.
• After that, navigate to this path: Computer ConfigurationAdministrative TemplatesSystem
• Next, look for the “Do not automatically encrypt files moved to encrypted folders” option and double click on it to set the policy. From there, you will see the following description:

“This policy setting prevents File Explorer from encrypting files that are moved to an encrypted folder. If you enable this policy setting, File Explorer will not automatically encrypt files that are moved to an encrypted folder. If you disable or do not configure this policy setting, File Explorer automatically encrypts files that are moved to an encrypted folder. This setting applies only to files moved within a volume. When files are moved to other volumes, or if you create a new file in an encrypted folder, File Explorer encrypts those files automatically.”

• Now select one of the radio buttons below depending on your preference:
  • Not Configured or Disabled: Enable Auto Encrypt of files moved to EFS Encrypted folders.
  • Enabled: Disable Auto Encrypt of files moved to EFS Encrypted folders.
• Then click on the Apply and OK buttons to save the changes made.
• Exit the Group Policy Editor and restart your computer.

If you suddenly encounter Activation Error codes such as 0xC004E016, 0xC004F210, 0xC004F034, and 0xC004F00F on your Windows 10 computer, then they all point to the same issue – Invalid Product Key or Version mismatch. When you see any of the aforementioned error codes above, it indicates that you are either entering a wrong product key or you are using an incorrect ISO when installing it on your computer. In such cases, you may see either of the following error messages:

“You are running Windows 10 Pro, but you have a valid digital license for Windows 10 Home.” Or: “The specified product key is invalid or is unsupported by this version.”

If you got the error code 0xC004F00F then it means that you’ve entered a product key for the Enterprise edition of Windows to activate Windows 10 Pro or Windows 10 Home. It could be that you have a key from your work and you accidentally use it on your Home PC. If you got the error codes 0xC004E016, 0xC004F210, then it means that you have entered a product key that is meant for a different edition or version of Windows. On the other hand, if you got the error code 0xC004F034 instead, then it means that you have entered an invalid product key or a product key for a different Windows version. Whichever error codes you have, refer to the possible solutions given below to fix the Invalid Product Key or Version mismatch Activation Error in Windows 10.

Option 1 – Try running the Windows 10 Activation Troubleshooter

The first thing you can do to resolve this Activation error is to run the Windows 10 Activation Troubleshooter. To do so, follow these steps:

• Go to Settings and then select Activation.
• After that, click on the Windows Activation and then troubleshoot. This will help you address most of the commonly found activation issues in Windows devices.

Option 2 – Try purchasing a new license

There is an exception offered by Microsoft – if you are connected to a Microsoft account prior to the hardware change, then you can most certainly use the same license key to reactivate Windows 10 again. Microsoft calls this an “Exception path” which should be fixed easily by the Windows Activation Troubleshooter as pointed out earlier. However, if the Windows Activation Troubleshooter isn’t able to resolve the error you can try purchasing a new license. In such rate case, even if you do have a Microsoft account available on your Windows 10 computer, and if Windows was never activated, this solution will not work. And if you haven’t connected your Microsoft account with your Windows 10 computer prior to the major hardware change, then your only option left is to purchase a new license. For you to do that here are some steps you can follow.

• To purchase a new Windows license, the first thing you have to do is click on the Start button > Settings > Update & Security.
• From there, go to Activation and select the “Go to Microsoft Store” option.
• After receiving your new license, you need to go back to Update & Security then go to Activation and select the “Change product key” option.
• Now update your Windows 10 computer using the new key and it should automatically activate your computer.
• Next, you have to create a Microsoft account or connect to your existing local account to your online account.
• Once the system links the key and the account, you need not buy a new license in case something like this happens again.

Note: If you are an IT administrator, you need to keep in mind that there is a limit to the number of times you can reactivate Windows on your computer. Moreover, if you don’t see any option to reactivate the license, and it is a work computer, you need to contact your organization’s tech support.

Option 3 – Try activating Windows 10 via mobile phone

Activating Windows 10 can also be done using your phone. Just note that you have to call Microsoft to do so.

• In the Start Search box, type in “Slui 4” and tap Enter.
• Next, select your country and click on Next.
• Keep the window open and call the toll-free number of the country you’re from.
• Afterward, a confirmation ID should be given by the automated system which you must take a note of.
• Finally, in the box on the window, type in the confirmation ID and click on the Activate button. That should do it.

As you know, Windows PowerShell is a useful command-line utility in Windows 10 that can be used to manage the Local Users and Groups which affirms the multiuser operating system principle of Windows 10. Although there are other GUI-based utilities used to manage the Local Users and Groups, there are some system administrators that would still like to use the command-line utility to manage these Local Users and Groups. So in this post, you will be guided on how exactly you can manage the Local Users and Groups using PowerShell on your Windows 10 computer. To get started, refer to the options provided below to manage both the Local Users and Groups using Windows PowerShell.

Option 1 – Manage the Local Users via Windows PowerShell

• You need to first open Windows PowerShell as an admin. To do that, just tap the Win + X keys and select the Windows PowerShell (Admin) option.
• After opening PowerShell, you need to execute the “Get-LocalUser” cmdlet so that you can find all the details about all the local user accounts in your computer which would include the Account Name, Enabled status, as well as description.

Note: On the other hand, you can also get the customized data about several objects that are related to your account. For instance, if you want to check when was the last time the Local account’s password was set, then you need to execute the “Get-LocalUser -Name root | Select-Object PasswordLastSet” cmdlet. Thus, the structure for this cmdlet is “Get-LocalUser -Name root | Select-Object *”. Here are the objects you can use to get different sorts of data:

• AccountExpires
• Description
• Enabled : True
• FullName
• PasswordChangeableDate
• PasswordExpires
• UserMayChangePassword
• PasswordRequired
• PasswordLastSet
• LastLogon
• Name
• SID
• PrincipalSource
• ObjectClass

Option 2 – Manage the Local User Groups using Windows PowerShell

• Like what you did earlier, open Windows PowerShell as admin and then execute the “Get-LocalGroup” cmdlet so you can get all the information about all the groups of all the local user accounts.
• Now if you want to create a new Local User Group, just execute the “New-LocalGroup -Name <NAME OF THE GROUP> -Description '<ENTER THE DESCRIPTION OF THE GROUP HERE>'” cmdlet.
• And if you want to add Local User Accounts to a specific group, just execute the “Add-LocalGroupMember -Group '<NAME OF THE GROUP' -Member ('NAME 1','NAME 2','<ROLE>') -Verbose” cmdlet. You could also use the “Get-Localuser -Name john | Add-LocalGroupMember -Group '<NAME OF THE GROUP>'” cmdlet for the same purpose.
• If you want to display all the User Accounts of a specific group, just use the “Get-LocalGroupMember –Group ‘ ’” cmdlet.
• Now if you want to remove a local user account from a group, all you have to do is use the “Remove-LocalGroupMember -Group '<NAME OF THE GROUP>' –Member <NAME OF THE LOCAL USER ACCOUNT>” cmdlet.

If you got an error message saying, The INF file you selected does not support this method of installation while trying to install a driver using the “Install” option in the right-click context menu, read on as this post will guide you in fixing the problem. The INF file mentioned in the error message is a text file that’s divided into different types of formatted sections. Each one of the sections is designed for a particular purpose. For instance, one section is designed to copy files or to add entries to the registry. INF files are used to install drivers. However, if something is wrong, you might encounter this error while installing a driver on your Windows 10 computer. To resolve this problem, you can try to download the driver again from the official manufacturer website or check if the driver is compatible with your computer’s operating system architecture or you can also try installing the driver from the Device Manager. For more details, follow the given options below.

Option 1 – Try downloading the driver again from the official website of the manufacturer

Usually, you shouldn’t encounter this kind of issue no matter what installation method you used on your Windows 10 PC. However, there are times when the driver itself is corrupted for some reason which is why you are unable to complete the installation and receive an error message instead.

Option 2 – Try checking if the driver is compatible with the OS architecture

It is possible that you’re getting this error if you have a driver that is compatible with a 32-bit system and you are trying to install it on a 64-bit system and vice versa. Thus, you need to check if the driver you are trying to install is compatible with your operating system if you haven’t done it when you’ve downloaded the driver from the website of the manufacturer. To check the system architecture, in the Start Search, type “msinfo32” in the field and hit Enter to open the System Information window. From there, you should see all the information about your operating system. In addition, you can also search “system information” in the Cortana search box and look for the System Type entry and open it.

Option 3 – Try installing the driver from the Device Manager

If you have the driver files on your PC and you have to update a driver, refer to the steps given below to be guided on how to install the driver from the Device Manager.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the driver you want to update, and then right-click on each one of them and select the Update Driver from the menu.
• After that, click on the “Browse my computer for driver software” option.
• Next, select the “Let me pick from a list of available drivers on my computer” option and then click the Next button.
• On the next screen, you should see the “Have Disk” option. Click on this option and then click on the Browse button to go to the location of the file. After that, you shouldn’t have any problem installing the INF file.

Option 4 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the “The INF file you selected does not support this method of installation” error. 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. To run the SFC command, follow the steps given below.

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

 Now restart your computer.

Blinking or Flashing Desktop After login - What does it mean?

Upon updating to Windows 10, some users might encounter a blinking or flashing desktop after logging in. This will result in a repetitive restarting of explorer or you won’t be able to make the start menu and shortcut keys work. In addition, the network icon might not appear in your taskbar as well. Other Windows 10 error messages include error code 0xc000021a.

Solution

Error Causes

Your blinking or flashing desktop after logging in might be the result of problems with the bushell.dll shell extension, which is a part of the Norton Security Suite. Another possible cause for this annoying problem is an issue with your display driver since not all systems will use the same display driver and will depend on what graphics card you use.

Further Information and Manual Repair

In fixing the bothersome blinking or flashing desktop after logging in problem, you can do a manual repair method to address the root problem. You need to be familiar with the Windows command line to successfully go through the process. However, if you are not knowledgeable or confident enough to do this on your own, it would be best to seek help from a professional. Or, you might want to consider using an automated tool to solve the issue.

You need to identify first what’s causing the blinking or flashing of your desktop after login to properly address the issue. The following methods can be done if your issue is caused by bushell.dll shell extension issue:

Method One: Forcefully Terminate Process

1. Press on Ctrl+Alt+Del then select Task manager
2. Start a Command Prompt as an administrator by choosing the File menu then Run New Task.
3. Type exe. Make sure to tick the checkbox “Create this task with administrative privileges.”

NOTE: Text input is most probably affected by the explorer restarts so you might need to repeatedly type some letters or to carefully input texts.

4. In the Command Prompt, type taskkill /f /im explorer.exe. This will stop the blinking or flashing.
5. Type cd “Program Files” afterward, type dir /s bushell.dll to locate where the dll is. (For example, purposes, use c:\program files\Norton Security Suite\Engine6422.5.2.15 as the location)
6. If the dll file is not found, you can try repeating step 5 but this time, use “Program Files (x86)” However, you can proceed with the next step if you already located where the bushell.dll is.
7. Type cd ”c:\program files\Norton Security Suite\Engine 6422.5.2.15” to change the name of the directory you found the dll in.
8. Type ren bushell.dll bushell-crash.dll
9. Restart now the system by typing shutdown /r /f /t o in the command line.

Method Two: Uninstall Programs

1. Log out then go to the sign in screen
2. Press the Shift key as you simultaneously click on the Power button on the screen.
3. Continue pressing on the Shift key as you click
4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
6. Click on the Startup Settings then select
7. Boot on Safe Mode by pressing 4 on your keyboard.
8. Log in then press Windows key + X.
9. Select the Device Manager then expand Display Adapter.
10. On your Display Adapter, right-click then select
11. Exit Device Manager
12. If in case you also have an older Antivirus utility, you should uninstall it as well.
13. Restart

NOTE: You might need to download the latest Video Driver on a working computer. Save it in a thumb drive then copy and install it on your computer. If in case there is no native Windows 10 driver, you can also download the latest Windows 7 or Windows 8.1 video driver. Afterward, install it in compatibility mode.

Method Three: Use Microsoft System Configuration Utility

1. Log out then go to the sign in screen
2. Press the Shift key as you simultaneously click on the Power button on the screen.
3. Continue pressing on the Shift key as you click
4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
6. Click on the Startup Settings then select
7. Boot on Safe Mode but this time, choose 5 to start in Safe Mode with networking.
8. Check if your problem is present or not in Safe Mode. If not, then you are on the right track.
9. Press on the Windows key + R then type msconfig to start up your exe file.
10. Click on the Services tab then choose Disable All. Afterward, click on
11. Once you’re prompted to reboot your computer, go ahead and reboot in Normal Mode. Check if the issue is still present.
12. If the blinking or flashing desktop after login is gone, then you can just do a process of elimination.
13. Start-up on your exe again then begin bringing up services a few at a time.
14. You can turn on all other services except for the following which causes the blinking or flashing desktop after login problem: Problem Reports and Solutions Control Panel Support •Windows Error Reporting Service.

Computer upgrades are the most common and most efficient ones. RAM upgrade is one of the easiest ones you can do and the most common ones but even as simple an upgrade as this one can cause certain issues. If you are experiencing error 0164, memory size decreased after RAM upgrade we are offering you solutions on how to fix this particular error and get your computer back in working order.

1. Change BIOS settings

   Enter your motherboard BIOS (usually by pressing the del key on startup) Load BIOS defaults Save changes and exit If the Error 0164: Memory size decreased issue persists even after loading setup defaults, then it must be configured manually inside the BIOS.

2. Clear CMOS

   Follow the instructions precisely:
   • Turn off all peripheral devices connected to the computer.
   • Disconnect the power cord from the AC power source.
   • Remove the computer cover.
   • Find the battery on the board. The battery may be in a horizontal or vertical battery holder or connected to an onboard header with a wire.
   If the battery is in a holder, note the orientation of the + and – on the battery. With a medium flat-blade screwdriver, gently pry the battery-free from its connector. If the battery is connected to an onboard header with a wire, disconnect the wire from the onboard header.
   • Wait one hour, then reconnect the battery.
   • Put the computer cover back on.
   • Plug the computer and all devices back in.
   • Power on the computer.