Cannot start new hardware device, Error 49

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

If you’re suddenly unable to launch or open Google Chrome or unable to load web pages, then it’s most likely that the files in Chrome have been corrupted or some plugin is taking up a lot of resources which is why you encounter an error message saying, “Google Chrome has stopped working”. And when you try to check the Task Manager, you’ll see that Chrome is really taking up lots of resources, however, when you check the Taskbar, strangely, you will see nothing. If you are currently facing this issue in Chrome on your Windows 10 PC, follow the given options below.

Option 1 – Kill Google Chrome’s process in the Task Manager

If you aren’t able to open Chrome, then maybe its process is running in the background and you don’t see the browser windows. If that’s the case, you may have to force quit the browser and then try to open it again.

• First, right-click on the Taskbar then select the Task Manager. And if the Task Manager is not responding, you can just use the Alt + Ctrl + Del keys and then select the Task Manager.
• After opening the Task Manager, under Processes, look for Google Chrome’s process which would most likely be named “chrome.exe”.
• Right-click on Google Chrome’s process and then select the End task option.
• Now try to open Google Chrome again.

Option 2 – Try checking if your antivirus program is blocking Google Chrome

There are instances when due to false-positive, a security or antivirus program might block Chrome which is why it failed to open properly. Thus, you can just disable the security program temporarily and then check if you can now open Chrome or not.

Option 3 – Delete the User Profile in Chrome

You can also try deleting the User Profile folder in Chrome. To do so, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Then copy and paste “%USERPROFILE%AppDataLocalGoogleChromeUser Data” and hit Enter.
• From there, look for a folder named “Default folder” and then copy the folder to another drive as a backup.
• After creating a copy of the folder, delete the Default folder.
• Next, open Google Chrome again and go to Settings > Advanced > Reset.

Option 4 – Disable the Extensions in Chrome

There are instances when issues on a browser are triggered or caused by some problematic extension. To find out which one of your extensions is causing the problem, disable them all first and then enable them back one by one.

• Click on the three-dotted icon for the menu located at the top-right corner of your screen.
• Then click on the More tools option and go to Extensions.
• From there, you will see a list of all the installed extensions in Chrome.
• Disable all these extensions and restart the browser.
• Now enable them back one by one to figure out which one of them is the culprit. You could also remove extensions that you no longer use.

Option 5 – Run the Chrome Cleanup tool

You might also want to try running the Malware Scanner & Cleanup tool in Chrome. This is a built-in tool that can help you get rid of any unwanted pop-ups, banners, ads, unusual startup pages, toolbars, and malware. Thus, it can help you to resolve the issue in Chrome.

Option 6 – Try to reinstall Chrome

If running the Malware Scanner & Cleanup tool in Chrome didn’t work out for you, you can try reinstalling it. To do so, follow these steps:

• Open the Settings app and go to System > Apps & features.
• From there, look for Chrome and uninstall it from your PC.
• Then go to the official website of Google Chrome and download its latest version and install it.

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

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

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.

What Is Installation Error 1628?

Installation Error 1628 is, as the name suggests, an installation error. When it occurs, a generic 1628 message is displayed to the user. When this message appears, it is either a problem with the install files or an issue with the InstallShield.

Solution

Error Causes

Installation Error 1628 is caused because every Windows-based program or application has been designed that such that it has to be installed on the computer for use. This installation process is important because it not only moves files to the appropriate location on one’s hard drive but also because the process creates registry entries in Windows System files. A vast majority of these programs and applications have a built-in tool that’s responsible for aptly performing this installation. This built-in tool is the InstallShield. This establishes that when this error occurs, it is either because of some unforeseen issue that occurred during the installation process or because of some problem with the InstallShield.

Further Information and Manual Repair

In order to keep this error from occurring in the future, some recommendations are outlined below.

• Check the installation disc and determine if there are any smudges, scratches, or fingerprints on it. If the system is unable to read data from the disc, Installation Error 1628 will be generated. In order to ensure that the Installation Disc is clean, use a microfiber cloth. Dampen it lightly with water and clean the disc. Wipe the inside of the disc lightly in an outward direction, making sure that it is not wiped in a circular pattern. Try to reinstall the application or program after cleaning the disc. The issue should be resolved. However, if it persists, some problems may be with the InstallShield.
• The alternative solution is to repair the InstallShield and the procedure goes as follows.

1. Stop InstallShield’s running process. It may have been crashed and simply needs to be restarted. Now access task manager. Press Ctrl+Alt+Del and the task manager will open. Now go to the processes tab and disable ‘idriver.exe’ and ‘msiexec.exe’ from here.
2. Now go to ‘C: Program Files/Common Files’. Here you will find the ‘InstallShield’ folder. Select ‘rename’ and modify the folder name to ‘InstallShield1’. Confirm rename and start the installation process again. Now Windows will try to re-install any InstallShield files one needs.
3. If the error persists after renaming the InstallShield folder, download the Windows Installer from Microsoft’s website. This file will determine whether or not your version is valid. Old versions often have bugs that cause problems. Your system is now ready to be used.

In case you don’t know, Windows contains a feedback mechanism that generates error reports from hardware and software problems. These reports are temporarily stored in the system and send them back to Microsoft so that it can find solutions to the reported problems and fix them in the upcoming updates.  However, as time goes by, these reports actually take a lot of space in your computer which is why end-users like you are free to delete them with the help of the new Free Up Space feature in Windows 10. As useful the Free Up Space feature may be, there are times when you won’t be able to use it for some reason which is why in this post, you will be guided on how to use alternative ways in deleting very large System queued Windows Error Reporting file, some of which may run in Gigabytes. Every time the Windows Error Reporting or WER sends out an error file and looks for a solution, the WER server at Microsoft sends out a solution instantly. And if the solution is under investigation or is unknown, then you will be notified about it right away and will be asked for more details. As mentioned, even though the Free Up Space feature in Settings will be able to clear the error reporting files, there are instances when it won’t be able to delete very large System queued Windows Error Reporting files. Alternatively, there is an option to delete these files using the Disk Cleanup Utility. Feel free to select which option you’d like to use to get rid of Windows Error Reporting Files.

Option 1 – Delete Windows Error Reporting Files via Settings

• Go to Settings.
• From there, go to System > Storage > Free Up Space and then click on it to launch it.
• Afterward, give it some time to populate all the files and folders. Once it’s done, select “System created Windows Error Reporting files” to mark its checkbox while leaving the other options unchecked.
• Next, click on the Remove files button to delete all the Windows Error Reporting files from your computer.

Option 2 – Manually delete the Windows Error Reporting Files

• Tap the Win + E keys to open File Explorer.
• Next, enable the Hidden Files view from the menu.
• Then go to C:/ProgramData/MicrosoftWindowsWER.
• From there, you will see various folders like LocalReportArchive, ReportArchive, ReportQueue, and Temp.
• Open each one of the aforementioned folders and delete the archive files. Note that these files will have names similar to “00c58c1f-b836-4703-9bcf-c699ca24d285”.

Note: If you are not able to delete any of these files, you have to take ownership of the folder. To do so, refer to these steps:

• Right-click on the folder and then select Properties.
• Next, click on the Edit button in the Properties window and click OK to confirm if you got a User Account Control elevation request.
• After that, select user/group from the permission windows or click on the Add button to add another user or group. It would be best if you add “Everyone” to give permission.
• Then check “Full Control” under the “Allow” column to assign full access rights control permissions.
• Now edit the permission to Full Control for “Everyone”.
• Click OK to save the changes made and then exit.

On the other hand, if you do not want to go through all these troubles in deleting the Windows Error Reporting files, you can just disable it especially if it already becomes a daily annoyance as the files generate every day and their sizes are mostly gigabytes. And besides, there are times when these files do not make it to the Microsoft WER server and end up only occupying a lot of space for nothing.

Both the DISKPART utility and the Disk Management are useful tools in Windows 10 that manage the disk space allocation, and so on. But these tools are not without errors as you could also encounter some when you run them. Recently, some users reported getting an error that says, “The selected disk is not a fixed MBR disk when trying to use the DISKPART utility”. Here’s the exact message of the error:

“The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks.”

This kind of error only occurs when you try to activate a disk partition on a UEFI system partition. However, the command works only if your computer is based on BIOS/MBR. The UEFI method has no concept of the active partition and since you have a UEFI system, the disk type is GPT instead of MBR. To simply put it, your BIOS needs the MBR disk type while the UEFI needs the GPT disk type. To fix the “The selected disk is not a fixed MBR disk when trying to use the DISKPART utility” error, there are various potential fixes you can try. You might have to disable Secure Boot, convert the disk to MBR or fix the Boot Manager. For more instructions, follow the options provided below.

Option 1 – Disable the Secure Boot in the BIOS

Disabling the Secure Boot in the BIOS settings is definitely recommended to resolve the issue. To disable Secure Boot, here’s what you have to do:

• First, boot your computer into Windows 10.
• Next, go to Settings > Windows Update. From there, check if there is anything that you have to download and install if you see any available updates. Usually, OEMs send and update the list of trusted hardware, drivers, and operating systems for your computer.
• After that, go to the BIOS of your computer.
• Then go to Settings > Update & Security > Advanced Startup options. If you click on Restart Now, it will restart your computer and give you all the advanced options.
• Next, select Troubleshoot > Advanced Options. As you can see, this screen offers you further options including System restore, Startup repair, Go back to the previous version, Command Prompt, System Image Recovery, and UEFI Firmware Settings.
• Select the UEFI Firmware Settings which will take you to the BIOS.
• From there, go to the Security > Boot > Authentication tab where you should see Secure Boot. Note that every OEM has its own way of implementing the options so it varies.
• Next, set Secure Boot to Disabled and set Legacy Support to On or Enabled.
• Save the changes made and exit. Afterward, your computer will reboot.

Option 2 – Try converting the disk to MBR

You can try to change the File System of the drive from GPT to MBR but before you do so, make sure that you create a backup copy of your data to an external drive. Once you have that covered, follow the steps below.

• Create a bootable Windows 10 media and boot your computer from it.
• Next, click on the “Repair your computer” option on the first Windows 10 installation setup window.
• Afterward, select the operating system partition from the given options and click on Next.
• Now select Command Prompt within the System Recovery options box and execute this command to initiate the Diskpart utility: diskpart
• Then type either one of these commands to view the list of all the Disk connects or the partitions on those disks formed: list disk or list volume
• After that, execute another one of these commands depending on the command you previously entered to select the disk or partition you want to select: select disk # or select volume #
• Now execute this command to clean your drive: clean
• Finally, execute this last command to convert the selected disk or partition as MBR: Convert MBR
• Restart your computer and check if the error is fixed.

Option 3 – Try to fix the Boot Manager

• You can start by booting into the installation environment for Windows 10 from an installation media.
• After that, click on Repair your computer and on the blue screen, select Troubleshoot and then select the Advanced options menu.
• From there, select Command Prompt and once you open it, enter each one of the commands given below by sequence.
  • bootrec /FixMbr
  • bootrec /FixBoot
  • bootrec /RebuildBcd
• Once you’re done executing the commands given above, type “exit” to close the Command Prompt window and then restart your computer and see if it fixed error code 0xc000014c.

Task View feature inside Windows 11 is actually a great feature, letting you quickly view open windows and virtual desktops. How Task view itself could be reached with keyboard shortcut combination of ⊞ WINDOWS + TAB some users will prefer this way of using it and thus button on the taskbar is something you do not want or need. There is a very easy way to remove mentioned button and I will show you how to do it. Right-click the taskbar button itself and click on Hide From Taskbar. That’s it, you have done it. Now in order for you to bring it back if you change your mind, you will have to do some extra steps but it is nothing difficult. Right-click on the taskbar and click on Taskbar settings, you will be lead to Personalization > Taskbar. Inside locate Taskbar Items and switch Task View to ON, you will see the Task View button right away showing itself again.

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.

Recently, a lot of users reported getting several error messages when they upgraded their Windows 10 computers. One of these error messages users encountered during a Windows 10 upgrade is the Error 0x8007002C-0x4001E. if you are one of the users who is facing this error, read on as this post will help you fix it. When you encounter this error, you will see the following error message on your screen:

“We couldn’t install Windows 10 We’ve set your PC back to the way it was before you started installing Windows 10 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.”

To resolve the 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase error, here are some suggestions that might help.

Option 1 – Try flushing the SoftwareDistribution and Catroot2 folders

You have to stop a couple of services such as BITS, Cryptographic, MSI Installer, and Windows Update Services. And to do that, you need to flush the contents in the SoftwareDistribution folder. The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net start cryptSvc net start bits net start msiserver

• After entering these commands, it will stop the Windows Update Service, Background Intelligent Transfer Service (BITS), Cryptographic, and the MSI Installer
• Next, go to the C:\Windows\SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.

After flushing the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:

• Type each one of the following commands.

net start wuauserv net start cryptSvc net start bits net start msiserver

• After that, exit Command Prompt and restart your computer, and then try to run Windows Update once more.

Option 2 – Select the Keep your files option

You can also select the option to perform an in-place upgrade and opt for the “Keep my files” option during an installation as it might make the process a lot smoother and if you need to perform a clean install, you can do so once the setup is completed.

Option 3 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the 0x8007002C-0x4001E, The installation failed in the SECOND_BOOT phase error. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button.

Option 4 – Try to run Microsoft’s online troubleshooter

Aside from the Windows Update Troubleshooter, you can also run the online troubleshooter of Microsoft as it can help you with Windows 10 upgrade errors.

Option 5 – Perform a clean install

If none of the options worked, you can try to clean install Windows 10. Just make sure that you have the ISO from the official Microsoft Website and then a bootable USB drive to install Windows 10 again. Take note that this will delete all the data from your drive where Windows 10 was installed previously.