How to Fix Dxgkrnl.sys Error Code

What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.

Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:

1. A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
2. The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
3. Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.

Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.

Option 1 – Try updating your PC to the latest Windows build available

Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.

• Tap the Win + R keys to open the Run dialog box.
• Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
• After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
• Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.

Option 2 – Try to change the Startup Type of the Remote Procedure Call service

As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason. In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:

• Tap the Win + R keys to open the Run dialog box.
• Type “services.msc” in the field and hit Enter to open Services.
• From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
• Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
• After that, click the Apply button and then OK to apply the changes made.
• Restart your PC and run the DISM command once again at the next startup.

Option 3 – Try to modify the RpcSs registry key value

If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.

• Tap the Win + R keys to open the Run dialog box.
• Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
• After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
• After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
• Next, change the Value data of start to 2 and click OK to save the changes made.
• Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.

Option 4 – Try to disable the Windows Search service temporarily

Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.

• Tap the Win + R keys to open the Run dialog box.
• In the field, type “services.msc” to open the Services window again and hit Enter to open it.
• Next, scroll down over the services list and double-click on the Windows Update service.
• Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
• Now try running the DISM commands again and see if the problem’s fixed or not.
• Restart the Windows Search service and then restart your PC as well.

Runtime Error 713 is an error that occurs during the distribution of a Visual Basic application that includes a data report. The error is displayed on the screen when you try to open the data report from your desired application.

Error Causes

The reason why computer users often experience the Runtime Error 713 is that the data report run-time file also referred to as Msdbrptr.dll is not included in your setup package. Though this error does not pose any big threat to your computer, however, it is recommended to fix the error because the Runtime error 713 may hamper your ability to install and access new programs.

Further Information and Manual Repair

Don’t you panic if you see Runtime Error 713 message pop up on your PC? This error is rated easy to repair and can be fixed in a couple of minutes. There are two ways to fix Runtime Error 713. You can choose whichever 2 alternatives suit you best.

• Method 1

First, open your project and include a reference to the data report file, the Msdbrptr.dll file. Locating this file is not difficult. It is listed as Microsoft Data Report Designer v6.0 in the reference dialog box. Sometimes you may see this file listed more than once. Now when this happens be sure to select the file that is associated with Msdbrptr.dll. After you select it, the reference will be verified. Once verification is complete, you are good to go. Now you can try rebuilding your setup package again.

• Method 2

The second alternative is to add the Msdbrptr.dll file manually in PDW (the Package and Deployment Wizard). Simply add the file in the Included Files dialog box window and run the PDW. Now you are all set to rebuild your setup package. Whether you follow method 1 or 2 after you rebuild the setup package and the installation is complete, you will see the following files in the indicated folders:

• <windows system>Msdbrptr.dll
• <program files>Common Files\Designers\Msderun.dll
• <windows system>Msstdfmt.dll

The presence of these files indicates successful installation and now you can easily try opening the data report. If you’ve noticed, all you have to do to fix Runtime Error 713 was to include the Msdbrptr.dll file. So, next time if you or your friends experience Runtime Error 713, you know exactly what to do and how to fix it.

RocketDock is one of the most popular app launchers as it has been used excessively back in several windows versions. This was modeled based on the Mac OS X launch bar and offers an animated response when you hover the mouse over the apps gathered on the Dock. This is perched at the top of your screen, and you can easily drag your favorite app icons to have them in one place. The dock keeps all your most favorite shortcuts intact for faster and easy access. Like other apps, you can easily customize the dock with skins and other add-ons. If you would like to read more helpful articles and tips about various software and hardware visit errortools.com daily.

Microsoft allows its users to download a copy of Windows to install on PCs. However, when you enter the key after the installation and you got the Activation Error 0xC004F212 instead, then it means that the license key and the Windows version you’ve just installed, do not match. When you encounter this error, you will see the following error message on your screen:

“The product key used on this PC didn’t work with this edition of Windows. Activation Error 0xC004F212.”

Every time Microsoft generates a license for a copy of Windows, it is associated with one particular Windows variant. Windows comes in many editions like Enterprise, Home, Professional, and so on. For instance, if you bought a license for Windows 10 Enterprise but you have installed Windows 10 Professional instead, then the activation will surely fail and you’ll encounter the Activation Error 0xC004F212. You will be asked to select which edition you want to install when you reinstall Windows 10 using a digital license. If you opted for an edition other than the one you are licensed to use, then you will most likely get the Activation Error 0xC004F212. If you have purchased your license key from a store or some website, you might want to check back with them about the exact version of Windows. Doing so will help you narrow down the problem. And if you have second thoughts about the license key’s validity, you can just reach out to a Microsoft Support agent to check the validity of the license key. Also, if have bought it from the store, there should be an option to get a refund. That way you can choose to buy the right version of Windows.

Option 1 – Try running the Windows 10 Activation Troubleshooter

The first thing you can do to resolve the Activation Error 0xC004F212 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.

The Windows 10 Activation Troubleshooter will determine if your license key is a valid Windows 10 digital license for an edition that is not currently installed. If it turns out that it’s not, then the troubleshooter will show you how to install the correct edition.

Option 2 – Try forcing Windows 10 ISO to use the right version

You can also try to force Windows 10 ISO to use the correct version depending on the product key. Note that this option only works between Windows 10 Home and Professional version since they both have a common ISO. So if it’s Enterprise, then this option won’t work for you.

• Extract the Windows 10 ISO files using an extractor.
• Then browse to the folder you created and go to the sources folder.
• From there, you need to create a text file named “PID.txt” and make sure to follow the exact format given below:

[PID] Value=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

Note: “xxxxx” is the KEY to your Windows version.

• Next, you need to create the ISO again or bootable media that will repack everything and then create the Media file. You can use the Media Creation tool for this.

Note: Windows will check the key during the installation and will figure out the right version of Windows.

Option 3 – Contact Microsoft Support for assistance

If you’re at your wits’ end in trying to update your Windows 10 computer, you should consider contacting Microsoft Support for help as they can offer you various options that would make fixing Windows Activation Error 0xC004F212 a lot easier and faster.

External hard drives have become essentials as they store data. However, they are also prone to issues and one of them is the “The device is not ready”. You could encounter this error when you try to access your connected hard drive. This error won’t allow you to access the contents of your hard drive so unless you fix it, you won’t be able to access any of the files on your hard drive. One of the most likely causes of this error is a hardware defect. Aside from that, it could also be due to loose connections, obsolete device drivers, as well as compatibility issues between the operating system and the hard drive. Before you start troubleshooting the problem, you need to determine if you were able to access your hard drive before you encountered the error or not. If not, you need to check the compatibility of the device with your operating system as it could be the reason why you’re getting the error. There are several potential fixes you can check out to fix this error. You can try to check the hardware connections, run the built-in Hardware and Devices troubleshooter, as well as the USB troubleshooter. You could also run the CHKDSK utility or update the drivers of the device or the USB drivers.

Option 1 – Try checking the hardware connections

The first thing you have to do before you further troubleshoot the problem is to check the hardware connections of your computer and see if there are damaged ones, just like with USB ports, it would also affect the overall connectivity of the device with the computer. So if you notice some irregularities in the connecting cable physically, you might have to buy another one and replace it and then see if it fixes the problem or not.

Option 2 – Run the Hardware and Devices Troubleshooters

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

Note: You could also try to run the USB troubleshooter as it could also resolve the problem.

Option 3 – Run the CHKDSK utility

As you know, the CHKDSK utility can help you in identifying the bad sectors in a drive and fix them automatically. Thus, you can run it to fix the “The device is not ready” error when you connect your USB drive to your computer.

• Open Command Prompt with admin privileges.
• Next, type and enter this command to execute it: chkdsk /f <drive>
• Now, wait until the process is completed and exit Command Prompt.
• Restart your computer and try connecting the USB drive again and see if the error is fixed.

Option 4 – Try to update the drivers of the device

Although you can always update the device drivers using the Device Manager, you might want to try downloading the latest set of drivers directly from the manufacturer’s website. Once you’ve downloaded them, install them right away and then correct the external hard drive.

Option 5 – Update or reinstall the Universal Serial Bus Controller driver

If updating the drivers of the device did not fix the “The device is not ready” error, you can try to update or reinstall the Universal Serial Bus Controller drivers instead of using the Device Manager. Refer to the following steps:

• 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 “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.

Note: If it is a regular USB drive, then it will be listed as a USB Mass Storage Device but if you have a USB 3.0 device, then look for a USB 3.0 Extensible Host Controller.

• Restart your PC and then click the “Search automatically for updated driver software” option.

Note: If updating the USB Controller drivers didn’t work, you can try to reinstall them instead.

Option 6 – Restart your computer in a Clean Boot State

If the first three given options didn’t work and you still see the error when you connect external devices, you can try putting your computer in a Clean Boot State and then try connecting them again.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• Now try to connect the external devices and check if the error is now gone.

Error Code 0xc00000fd - What is it?

In its most basic essence, Error Code 0xc00000fd appears when a program can not be initiated. It can occur when a file or program is corrupted, incompatible with the current version of the operating system, or out of date.

This error code occurs primarily in Windows but is also present in previous editions of the operating system. The symptoms of this error and the resolution methods for each of these systems are essentially resolved in the same way.

Common symptoms include:

• Failure of programs to open properly, even if they were able to be opened in the past
• The appearance of an error message stating that the application couldn’t be started correctly

There are several different things that Windows 10 users can do to try to fix the appearance of Error Code 0xc00000fd on their machine. Some of these methods are fairly simple for the average user, while others may require advanced knowledge and comfort with diving into the deeper tools and settings of the Windows operating system. If you have difficulty in implementing the methods below, contact a qualified Windows repair technician to assist you in the resolution of the error code.

Solution

Error Causes

Error Code 0xc00000fd can arise when program files are not recognized properly by the operating system, when the operating system is no longer compatible with the program being run, when files are missing or corrupted, or when the program has been changed in a substantial way. Each of these causes requires a different method of resolution.

Further Information and Manual Repair

Several methods can be used to attempt to resolve Error Code 0xc00000fd on your computer. Basic users can use some of these methods, while others require familiarity with advanced tools and options in Windows. If you have trouble implementing the steps below, contact a qualified professional to assist you. Here are the top ways to deal with Error Code 0xc00000fd on your machine:

Method One:  Check for Updates using the Windows Update Tool

In some cases, compatibility issues can be resolved through updates and patches available directly from Microsoft via the Windows Update tool. This is most likely the case if you have not kept up with regular updates on your machine over time. In your settings, open up the Windows Update tool and run a scan to see if there are any required updates available for your programs or for the operating system itself. If there are updates, install them, then reboot your computer to make sure that all updates are able to be fully applied to your operating system. Attempt to open the program that caused the error after you are finished to see if this method addressed the problem fully or if an additional method needs to be used.

Method Two:  Roll Back to an Earlier Version of the Updates

Sometimes, an update can cause a compatibility issue. If you have previously been able to open the program in question without any problems, but have recently installed an update on your computer, that update may have been the source of the problem. If this is the case, roll your system back to an earlier stage of updates to see if that fixes the problem. If so, you may need to wait to reinstall the updates until Microsoft corrects the issue.

Method Three:  Run Scans on Your Registry, Antivirus Software, Drivers, and Update Troubleshooters

If there truly is a corrupted or missing file within the program that you are trying to run, you can open up several tools to scan for the file that may be causing the trouble and attempt to fix it. Run the following tools to try to fix the problems:

• Windows Registry Repair Tool (this particular tool may take some time to complete)
• Windows Update Troubleshooting Wizard
• Windows Drivers Updates
• Antivirus software or Microsoft Security Essentials

After running each of these tools, restart your computer to allow any necessary changes to be applied to your system. If the above methods do not fix error Code 0xc00000fd on your particular device or if you do not have the confidence and knowledge to implement these steps on your own, get in touch with a Windows repair professional who can help you to resolve the problem.

Method 4: Use An Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 10 and other related issues when they do arise, download and install a powerful automated tool.

Connapi.dll Error Code - What is it?

Connapi.dll is a type of dynamic link library file. This file contains small programs like any other DLL file and is called to load certain programs on your PC. The Connapi.dll error message occurs either when using or installing programs. This error message is displayed in either of the following messages:

“Connapi.dll Not Found" "This application failed to start because connapi.dll was not found. Re-installing the application may fix this problem." "The file connapi.dll is missing." "Cannot start [APPLICATION]. A required component is missing: connapi.dll. Please install [APPLICATION] again." "Cannot find [PATH]connapi.dll"

Solution

Error Causes

Connapi.dll error may occur due to numerous reasons on your PC. The most common causes include:

• Missing Connapi.dll file
• Corruption of the Connapi.dll file
• Driver Issues
• Viral Infection
• Registry Issues such as bad and invalid entries

This error may hamper your ability to access your desired programs causing you a great deal of inconvenience. And if the underlying cause of the error is related to the registry, then your computer can be at serious risks like system failure and crash.

Further Information and Manual Repair

To resolve Connapi.dll error code on your PC, here is a list of solutions. These are easy, very simple to perform, deliver the best results, and more importantly require no technical expertise.

Solution 1: Check your Recycle Bin - You May Have Deleted the File Accidentally

As dll files are shared files, it is possible that you accidentally deleted the Connapi.dll file while uninstalling a program from your system. In such a situation, go to the recycle bin and look for the file. If you find the missing Connapi.dll file, simply restore it and then try running your desired program again. If the program runs, then the error is resolved. However, if it still persists, then try other solutions given below.

Solution 2: Update the Drivers

Try updating drivers for hardware devices on the system. To do this, go to the start menu and then Control Panel. Double click on Add or Remove programs icon. Now select incompatible drivers and remove them. After that, restart your PC to activate changes. Now go to the manufacturers’ website to download new drivers and install them on your PC.

Solution3: Scan for Viruses

Another solution is to scan for viruses and malware. Sometimes these can also damage and corrupt dll files on your system. To perform a scan, simply download a powerful antivirus program and run it.

Solution 4: Clean and Restore the Registry

If the error code is still there, then this means the problem is triggered by the registry issues. To resolve it you must clean the registry and remove all the unnecessary and obsolete files like junk files, internet history, temporary files, and cookies. The best way to clean these files instantly is to install Restoro. This is an advanced, cutting-edge, and multi-functional PC Fixer. It has a user-friendly interface and is integrated with powerful utilities like a registry cleaner, anti-virus, and a system optimizer. It is compatible with all Windows versions. The registry cleaning feature scans your entire PC in seconds and detects all the registry issues. It removes all the bad registry entries and unnecessary files. Simultaneously, it also fixes the system files and dll files like Connapi.dll. The anti-virus utility removes all types of malicious software on your system while the system optimizer utility ensures your system performs at its optimum speed. To resolve Connapi.dll error, click here to download Restoro.

Windows 11 is a good-looking operating system but people love to make things personal and to their liking so we decided to help you in this mission with small customization of changing default system fonts inside Windows 11.

Since there is no really easy way to just switch the font windows is using for itself we will have to tweak a registry a little so before we start please do make a backup of the registry file and follow the steps as they are presented in order to avoid any errors and break the system.

So, if all precautions are made and you are ready to change your Windows appearance let's dive right into it:

Find and/or install the font that you wish to use

There are vast free font sites on the internet where you can find fonts that you like and wish to use but be very careful with your desired font selection. The font that you choose needs to be a complete typeface, meaning that it has to contain all glyphs, large and small font sizes, all special characters, etc or you will experience that in certain areas nothing will be displayed.

Once you have found the font that you like and made sure it is a complete font, install it on your system (you can skip this step if you just want to change the system font with one already installed on your system)

Create REG file

Open notepad or a similar plain text editor in order to create a file that will apply changes directly into the registry and create a new file. Inside the file paste this text:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"=""
"Segoe UI Bold (TrueType)"=""
"Segoe UI Bold Italic (TrueType)"=""
"Segoe UI Italic (TrueType)"=""
"Segoe UI Light (TrueType)"=""
"Segoe UI Semibold (TrueType)"=""
"Segoe UI Symbol (TrueType)"=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]

"Segoe UI"="NEW-FONT"

All the way to the bottom where it says: "Segoe UI"="NEW-FONT", change NEW-FONT with the font name that you have chosen or installed in the previous step. For example: "Segoe UI"="Ubuntu".

Now go to File > Save As and name your file however you want but give it REG extension so it looks like: my_new_windows_font.REG

Apply changes

Now that you have your registry entry saved, locate it and double-click on it, at this stage Windows warning will probably pop up, you can just ignore it and click on YES since you wrote the file and know what it is. After registry entry is applied reboot your PC in order for changes to take effect.

Rolling back

If you want to change the font to another one, just repeat this procedure again. If you want to roll back to using the default Windows font, repeat the process but with this code instead of the one provided in the REG file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts]
"Segoe UI (TrueType)"="segoeui.ttf"
"Segoe UI Black (TrueType)"="seguibl.ttf"
"Segoe UI Black Italic (TrueType)"="seguibli.ttf"
"Segoe UI Bold (TrueType)"="segoeuib.ttf"
"Segoe UI Bold Italic (TrueType)"="segoeuiz.ttf"
"Segoe UI Emoji (TrueType)"="seguiemj.ttf"
"Segoe UI Historic (TrueType)"="seguihis.ttf"
"Segoe UI Italic (TrueType)"="segoeuii.ttf"
"Segoe UI Light (TrueType)"="segoeuil.ttf"
"Segoe UI Light Italic (TrueType)"="seguili.ttf"
"Segoe UI Semibold (TrueType)"="seguisb.ttf"
"Segoe UI Semibold Italic (TrueType)"="seguisbi.ttf"
"Segoe UI Semilight (TrueType)"="segoeuisl.ttf"
"Segoe UI Semilight Italic (TrueType)"="seguisli.ttf"
"Segoe UI Symbol (TrueType)"="seguisym.ttf"
"Segoe MDL2 Assets (TrueType)"="segmdl2.ttf"
"Segoe Print (TrueType)"="segoepr.ttf"
"Segoe Print Bold (TrueType)"="segoeprb.ttf"
"Segoe Script (TrueType)"="segoesc.ttf"
"Segoe Script Bold (TrueType)"="segoescb.ttf"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes]

"Segoe UI"=-

As you know, Windows Updates are essential for your operating system as it keeps it protected from potential threats, fixes bugs and improves your experience in using Windows 10. However, there are instances when Windows Updates also cause errors and one of them is the Windows Update Error 0x8024000B. One of the causes of this particular Windows Update error is that Windows was not able to read the Update Manifest file which is needed to install the Windows Updates. This means that the operation was canceled by either the service or the user. On the other hand, this error could also occur if you are not able to filter the results. When you encounter this error, you will see an error message that says, “WU_E_CALL_CANCELLED: Operation was canceled”. This indicates that the operation was canceled by the operating system itself. To resolve the Windows Update Error 0x8024000B, here are some suggestions you need to check out.

Option 1 – Try to run the Cleanup (Decline) Superseded updates PowerShell script

The first thing you can do to fix the Windows Update Error 0x8024000B is to run the Cleanup (Decline) Superseded updates PowerShell script. This is actually an easy fix since all you have to do is download and run it from the Microsoft Technet site. Once you’re done downloading and running the file, restart your computer and see if the error is fixed or not.

Option 2 – Try to rename the Spupdsvc.exe file

If the first option didn’t work, you can try renaming the Spupdsvc.exe file which is one of the reasons why you’re getting the Windows Update Error 0x8024000B.

• First, tap the Win + R keys to launch the Run utility.
• Next, type the following command and hit Enter to execute it in cmd:

 /c ren %systemroot%System32Spupdsvc.exe Spupdsvc.old

• The command you entered will rename the troublesome “Spupdsvc(.)exe” file to “Spupdsvc(.)old”.
• Now restart your computer after the command has been executed.

Option 3 – Try to restart various Windows Update-related services and components

You could also try to restart some Windows Update-related services to resolve the Windows Update error. Refer to the following steps to do so:

• Tap the Win + X key combination and select Command Prompt (Admin) to open Command Prompt with admin privileges.
• After opening Command Prompt, copy and paste each one of the commands listed below one by one and tap Enter right after you enter each command.
  • net stop wuauserv
  • net stop bits
  • net stop appidsvc
  • ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
  • ren %systemroot%system32catroot2 catroot2.bak
• Once you’ve entered all the commands given above, they will stop all the Windows Update services that are running on your computer as well as clear the SoftwareDistribution folder, and reset the Catroot2 folder. Now you have to start all these Windows Update services you’ve just stopped by executing the following commands:
  • net start wuauserv
  • net start bits
  • net start appidsvc
  • net start cryptsvc
• After that, restart your computer and try to run the setup again, and see if the error is now fixed.

Option 4 – Try to run the Windows Update Troubleshooter

You should also try to run the built-in Windows Update troubleshooter as it could help you resolve the Windows Update Error 0x8024000B. To run it refer to these steps:

• Go to Settings and then click on Windows Update from the given menu.
• Next, click on the Troubleshoot option and select Windows Update from the given options to run the Windows Update troubleshooter.
• After that, follow the next on-screen instructions and wait until the process is completed, and check if the Windows Update Error 0x8024000B is fixed or not.

What is Error 1706?

Error 1706 is a Windows PC error. It occurs when you insert a Microsoft CD-ROM either to repair an Office or to install a feature set to Installed on First Use. The error message is displayed in the following format: Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:\Program Files\Microsoft Office\Office101033\Setup.hlp.

Solution

Error Causes

Error 1706 may occur due to several reasons. These include:

• You originally installed MS Office from a network administrative installation
• You are trying to use Office CD-ROM when the error is prompted by the Windows Installer for an Office source location
• Viral Infection

Further Information and Manual Repair

The good news is that this error code is not fatal. However, to avoid inconvenience, it is recommended to resolve the error right away. To fix the problem you don’t have to be a computer programmer or hire one. In fact, this error code can be resolved quite easily. Here are some of the best and easiest do it yourself methods to resolve error 1706 on your PC:

Method 1

To resolve this issue find a different administrative installation for the Office source file location. To do this, go to the start menu and then click run. In the open box, simply type this command line new network pathSetup.exe /fvm package name.msi and press OK to continue and update changes. Once the update is complete and finished press OK to save and proceed. Please note after you follow these steps, the Windows Installer uses this new server location whenever it needs to reinstall, repair, or add a feature to your Office Installation.

Method 2

Another alternative method to resolve this method is to use CD-ROM for the Office Source Location. To do this you will have to remove Office and then re-install Office from the CD-ROM. Here are the steps to remove the Office program. First, quit all Office programs.

1. Go to the Control Panel then click on the Program and Features option.
2. Now double click the Add/Remove programs and remove the entry for the Microsoft Office 2003 or Microsoft Office XP product installed on your PC.
3. After that, click on the Maintenance Mode Options dialog box, select Uninstall Office, and then click Next to proceed.
4. Click Yes to confirm changes.
5. Now insert Office 2003 or Office XP CD-ROM and follow the setup dialog boxes to reinstall the program on your system from CD-ROM.

Download Restoro to Correct Registry Errors

However, to ensure the installation is successful this time around, it is advisable to clean the registry and ensure the uninstalled program is not located in the registry. To do this, download Restoro and run it on your computer. This is a powerful PC Fixer integrated with a registry cleaner. The registry cleaner wipes out all the unnecessary files and uninstalled program files saved in the registry. Once the registry is cleaned, try reinstalling MS Office again. This will resolve the error 1706. Click here to download Restoro and repair error 1706.