Removing Default Taskbar Buttons in Windows 11

Error 400 - What is it?

Error 400 is a bad request error that displays in the internet browser like a web page. It pops up when the web page you’ve requested cannot be found. Error 400 may be displayed in one of the following formats on the computer screen:

• ‘400 Bad Request’
• Bad Request - Invalid URL"
• "HTTP Error 400 - Bad Request"
• "Bad Request. Your browser sent a request that this server could not understand.”
• "HTTP Error 400. The request hostname is invalid."
• "400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications."

Solution

Error Causes

Error 400 can be generated due to multiple reasons. These include:

• Wrong URL
• Browser cookies
• Outdated DNS cache

Though this error code is not fatal like the blue screen of death and runtime errors nonetheless it is still advisable to fix it to access your desired website without any inconvenience.

Further Information and Manual Repair

Here are some of the best ways to fix error 400 on your PC without any professional help. Try these methods to resolve error 400:

Method 1

This might come to you by surprise that the most common cause for a 400 Bad Request error is because the URL of the website was typed wrong. So, first things first make sure the URL you’ve inserted is correct. If the URL typed is correct, then try other methods illustrated below.

Method 2

Sometimes error 400 may pop up due to outdated DNS records. DNS cache stores the location (IP addresses) of web servers that contain pages that you’ve viewed recently. You are unable to access the site if the location of the webserver changes before the entry in your DNS cache updates. If this is the error cause then simply clear your DNS cache to resolve. Follow these steps to clear the DNS cache on Windows 8.

• Press Win+X to open the WinX menu.
• Now ‘right click’ on command prompt and select RUN as Administrator. Enter the following command:
• ipconfig /flushdns

If the command was successful, you will see the following message: Windows IP configuration successfully flushed the DNS Resolver Cache. This method will hopefully repair error 400 on your computer screen.

Method 3

Another reason for error 400 can be browser cookies. Many sites report error 400 when a cookie it reads is corrupt or too old. In such a situation it is advisable to clear your browser cookies. You can do it manually but it can be time-consuming virtually because the steps involved in deleting cookies differ considerably depending on what web browser you’re using. So, to avoid the hassle it is advisable to download Reimage to remove browser cookies immediately. This is a user-friendly PC Fixer deployed with a powerful registry cleaner. It removes all obsolete and unnecessary files from your PC including junk files, internet history, and cookies in seconds. Click here to download Restoro.

We have gathered and want to share with you all of the Windows 11 wallpapers if you would like to place them on your desktop now and now wait for the official W11 release. Hope that you will like some of them and I hope to see you again on errortools.com Download Windows 11 Wallpapers here!

And here is the preview of them

Black Screen During Installation - What Is It?

Many are upgrading their OS to Windows 10, however, it’s not always smooth sailing because users have been reportedly experiencing different bugs including Black Screen after a successful update.

One common issue in installing Windows 10 is the appearance of a black screen after installation. This usually occurs when the user restarts the computer. Initially, there will be a black screen only appearing on the monitor. There are also cases where a mouse cursor is present, while some cases have no cursor at all.

Not only that, it seemed that you’ve lost all your desktop icons when experiencing this bug.

Solution

Error Causes

Just like the other bugs experienced by Windows 10 users, booting to a black screen has reasons. Before you even try to look for the solution, you first have to determine the cause of the error, in this case, the error would be black screen when booting.

• Error on external devices such as printer or mouse.
• Having outdated display/video drivers that normally result in black screen when OS is updated.

If error messages are left unsolved, you may encounter other Windows 10 related issues such as error code 0xc0000142. 

Further Information and Manual Repair

Before you even think of upgrading your OS to Windows 10, you need to know that there are specific system requirements and specifications to be able to successfully update your operating system.

• Minimum of 1 gigahertz (GHz) Processor
• Either 1 (GB) (32-bit) or 2 GB (64-bit) Ram
• You need at least 16 GB of free hard disk space
• A Microsoft DirectX 9 graphics device or later with WDDM 1.0 driver graphics card
• 800 x 600 display
• A Microsoft account and Internet access.

There are more system requirements in order to use other certain Windows 10 features, but we’ll focus on solving your black screen problem in this article.

IMPORTANT NOTE: While it’s possible that you’ll be able to find the solution for your black screen during Windows 10 update, contacting the service of a professional technician or using an automated tool is advisable if you’re not confident in performing the methods to be discussed.

Method 1: Windows 10 DVD Boot

1. Hit Repair your computer at the Install Now screen.
2. Press Advanced Options
3. When you’re in the Advanced Options find Troubleshoot and click it.
4. Proceed to pressing Startup Repair
5. Simply follow the instructions of the screen and check if that helps solve the black screen problem.

Method 2: Safe Mode from Windows 10 DVD Boot

1. Go to Install Now screen
2. Hit Repair your computer button
3. Go to Advanced Options
4. Click Safe Mode option

There’s a chance that you’ll get an error prompt saying, “installation cannot be completed in safe mode.” If this happens, simply press Shift + F10. This command will redirect you to the Command Prompt. You just open Device Manager by keying in devmgmt.msc then disable the display adapters, now check if you’ll be able to successfully boot in normal mode.

This process will normally allow you to complete the Windows 10 installation, if that’s the case you can just update the display adapter drivers from the manufacturer’s website. Restart your computer and see if this solves the problem.

Method 3: Driver Roll Back

1. Hit Windows Key + X then press the Device Manager
2. Expand the Display Adapters option
3. Right-click the listed Display Adapter and press on properties
4. Find the Driver Tab and click on it, then press Roll Back Driver

Do take note, however, that the Roll Back Driver option is not available if there was no previous version installed.

Method 4: Check External Devices

Since one common cause of black screen during a Windows 10 update is the external devices you use in your computer, you might want to consider these steps as well.

1. Simply unplug all of the external devices you currently use
2. Restart your computer
3. If in case this solved your black screen problem, carefully plug back the devices one at a time to determine which of the device is the culprit.
4. Update the drivers for the outdated hardware using a reliable third party tool.

Method 5: Fast Startup Disabled

Some Windows 10 users had success in solving their black screen problem by disabling the fast startup.

1. Go to the Control Panel, find Power Options and press “Choose what the power button does,” which is located in the left pane of the panel.
2. Hit the “Change settings that are currently unavailable.”
3. Make sure to unmark the checkbox button saying, “Turn on fast startup.”

What is the Ieframe dll Error?

Ieframe.dll is a Dynamic Link Library, a collection of small programs. It is stored in C:\WINDOWS\SYSTEM32. The function of this dll file is to convert Html code into web pages on IE (Internet Explorer). When this file gets corrupt, you start experiencing ieframe.dll errors on your system. Ieframe.dll error is displayed in either of the following formats:

• "Res://ieframe.dll/dnserror.htm#"
• "Cannot find the file ieframe.dll"
• "File Not Found C:WINDOWSSYSTEM32IEFRAME.DLL"

Solution

Error Causes

The Ieframe dll error code may occur due to multiple reasons. These include:

• Incorrect Firewall settings
• Ieframe.dll corruption and damage
• Missing Ieframe.dll file
• Internet Explorer issues
• Viruses and malware attack
• Outdated security software applications

If you wish to continue browsing on Internet Explorer, then it is important for you to resolve this error right away.

Further Information and Manual Repair

Here are some of the best solutions to resolve the Ieframe dll error on your PC:

Cause: Missing Ieframe.dll file

Solution: If Ieframe dll error file is missing, this means you have either accidentally deleted it while uninstalling a certain program that also shared this file. Therefore the best way to resolve the issue is to restore the missing Ieframe.dll file. To do this check the recycle bin. If you find the file, simply restore it in the following path C:\Windows\System32. However, if you are unable to find it, then download it from a reliable website.

Cause: Incorrect Firewall Settings

Solution:  In case the error is generated due to incorrect Firewall settings, then try disabling this software.  See if this works and resolves the error.

Cause: Internet Explorer Issues

Solution: Sometimes the Ieframe dll error can occur due to Internet Explorer issues. Here it is recommended to reinstall and update the latest version of IE on your system. This can be done by removing the program from the system. Go to the Control Panel, click Add/remove programs, and uninstall the program. After uninstalling the old version, install a new and updated version of IE on your system and try running it again. If it works, great the error is resolved. However, if it persists, then this means the problem is deeper and bigger than you think. The reason can be severe viral infection and malware attack not just damaging Ieframe.dll file but also exposing your system to privacy errors and threats.

Cause: Damaged and Corrupt Ieframe.dll files

Solution: The files can get corrupt when the registry overloads with data. It stores important and unnecessary files like junk files, cookies, internet history, temporary files, and invalid registry entries. Such files take up a lot of disk space and damages dll files. To resolve this issue it is advisable to download Restoro. This is a powerful registry cleaner, that detects and resolves all registry issues in seconds. It wipes out unnecessary and obsolete files cluttering the registry and restores the damaged Ieframe.dll files. It is efficient, safe, and compatible with all Windows versions. It has an intuitive interface and easy navigation which makes it simple and easy to use.

Cause: Viral Infection

Solution: If the underlying cause is a viral infection, Restoro takes care of that too. It is more than a registry cleaner. It is embedded with a powerful antivirus that removes all malicious software from your PC including viruses, Trojans, spyware, malware, and adware. And unlike a typical antivirus, it does not reduce the speed of your system. Its system optimizer utility boosts your PC speed dramatically. Click here to download Restoro on your PC today and resolve Ieframe dll error today!

Windows Setup in Continuous Reboot Loop – What is it?

After upgrading to Windows 10 operating system from Windows 7 or Windows 8/8.1, a lot of Windows users are complaining about the Windows setup in a continuous reboot loop. The computer would just keep on rebooting every time the machine is booted and this incites frustration for a lot of Windows users.

Solution

Error Causes

When Windows launched the third update for Windows 10, users trying to upgrade to Windows 10 encountered an endless reboot loop problem. The computer will crash repeatedly. The KB3081424, which is a roll-up of bug fixes of Windows 10, continuously fails once you start the update process and then triggers a message showing: “We couldn’t complete the updates, undoing the changes.” The undoing process will then cause a system reboot mandatorily.

Once you log back on your computer again, the Windows 10 update will try to reinstall KB3081424. You will not be able to stop the update which will cause your Windows setup in a continuous reboot loop.

The KB3081424 will not be successfully installed since if it fails for the first time, that initial failure can be detected to create a bad entry in your Windows 10 registry. This will then prevent your subsequent attempts to reinstall KB3081424 to make it work correctly.

Further Information and Manual Repair

In order to fix the problem of Windows 10 setup in a continuous reboot loop, there are a few methods you can try. Try following these simple steps and you’ll be able to get rid of the problem.

Note: If you’re not highly confident to solve this issue on your own, it is highly recommended to consult an authorized computer technician who would be knowledgeable enough to fix the issue for you. In addition, you can also use a system optimizer to resolve the issue.

Method One: Check For Windows Update

Microsoft Windows released an updated fix for the Windows setup in continuous reboot loop problem. You can try fixing the issue through Windows Update.

1. Open Settings
2. Go to Update & Security
3. Select Windows Update then choose Check for updates

At this point, an additional update will be installed and downloaded to your operating system to resolve the continuous reboot loop problem.

Method Two: Eliminate Bad Registry Entry

Before KB3081424 attempts to install again, you can try doing this solution:

1. Click on the Start menu then type regedit
2. Once the window opens, go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
3. Create a backup for your registry key (since this process is a bit risky). Select ProfileList then click on File and Export then choose your backup name.
4. From the ProfileList IDs, remove anything with ProfileImagePath in it.
5. Close Regedit then reboot. By this time, the KB3081424 should properly install.

Method Three: Perform A Startup Repair

Another thing you can try to solve the Windows setup in continuous reboot loop problem is to perform a startup repair from a working computer.

1. Ensure that all unnecessary devices are disconnected from your computer as your computer might detect them.
2. If you are connected to a network, you need to disconnect from this as well.
3. On a working computer, download the Windows 10 ISO then you can perform a startup repair.
4. Boot your computer from the Windows 10 DVD.

To change your BIOS option to boot from the Windows 10 DVD, follow these steps:

1. Boot your computer then press the F2 function key to enter setup.

NOTE: You must do this quickly since the BIOS loads rapidly.

2. Once you’re inside the BIOS, navigate to the Boot Configuration screen. On this screen, you’ll be able to change the first device to be loaded.
3. Go to Removable Devices then hit Enter. Removable devices could either be a thumb drive or DVD. Select DVD to put it at the top and be the first boot device.
4. Save your changes by pressing on the F10 function key. A setup confirmation box will appear with a message Save configuration changes and exit now. Select Yes.
5. Exit BIOS by pressing on the ESC key. You should be prompted to boot from the Windows 10 DVD at this point.

If you're not able to execute the aforementioned processes on your own, get help or download and install a powerful system optimizer to assist with the windows continuous reboot loop process and other Windows 10 error messages.

The previous Windows versions all came with Microsoft's browser Internet Explorer. A lot of users love it because not only that it is easy to use. It is also very fast. Users didn’t have to worry about compatibility because it is almost always compatible with its Windows Version. When they introduced Windows 10, they changed the name of the browser from Internet Explorer to Microsoft Edge. It is faster and more user-friendly compared to its predecessors. But after the Creator Update, some experienced receiving the inet_e_resource_not_found error code. In contrary to what everyone expects, you actually don’t have to uninstall and reinstall the Microsoft Edge App. What you can do is reset the browser in your Apps & Features Settings in your Microsoft Settings.

To reset the browser you can follow the steps below:

1. Click on the Windows icon and go to settings.
2. Click on Apps and this will bring you to the Apps & Features page. Look for Microsoft Edge from the list of Apps and click on it.
3. Choose Advance Option
4. Scroll down then Under Reset, click on repair or reset. When you repair it will fix the existing problem but the data that caused the problem may still be present and can still cause problems. If you click on reset, it will delete all the cache and cookies that are installed in your browser but it will save your Favorites as well as your bookmarks.

Another way to resolve this is by disabling the feature TCP Fast Open on Microsoft Edge. To disable this, go ahead and follow the steps below:

1. Open the Microsoft Edge browser.
2. Type in about: flags on the Address (URL) bar.
3. Under Networking, uncheck the Enable TCP Fast Open.
4. Close your Microsoft Edge browser and open a new one.

Flushing the DNS also worked for other Users. Sometimes, the error code the inet_e_resource_not_found is caused by a corrupted DNS cache. There are 2 ways to flush your DNS. The first option is to use the command prompt to run the command.

1. To access the Command prompt or CMD, you can search for it on Cortana or you can click on the Windows icon to access the Programs, scroll down to the Windows System folder and click on it.
2. A dropdown menu will show up, click on Command Prompt which is the first on the list.
3. Type in the code ipconfig /flushdns and press enter.
4. There will be a message that will show that says Windows IP configuration successfully flushed the DNS Resolver Cache
5. Exit the CMD by typing exit and press enter.

The easiest way to do this is to Press the keys Window + R on your keyboard. Type in ipconfig /flushdns in the search box and hit enter or click on OK. These are only some of the ways to resolve the inet_e_resource_not_found. There are other ways to further troubleshoot this issue such as reinstalling your Wifi Adapter Driver or adjusting the DNS Server Address. But most of the time, users are able to resolve the issue with the steps provided above.

Windows 10 has a Cloud Clipboard feature that allows users to have a list of multiple copied text in place so that they can reuse it. And each time the computer restarts, the Clipboard Data is cleared. However, you can actually do it manually. How? Read on as this post will walk you through how you can turn on or off as well as clear the Clipboard history in Windows 10. This kind of feature is already available in Windows 10 v1903. In the previous versions of Windows, there was no feature to turn off history in the clipboard and users have to use other ways to clear the clipboard history. And now it seems that Microsoft has put an end to this dilemma as it now allows users to clear the clipboard history. To turn on or off or clear the Clipboard history, here are some instructions you need to follow: Step 1: Tap the Win + X keys to open the power menu and select Settings. Step 2: After that, navigate to Settings > System > Clipboard. Step 3: From there, turn off the toggle button under the Clipboard history section. This will turn off the Cloud Clipboard feature. As a result, the default clipboard will hold one last item and will not display the data on the clipboard. Note: When you tap the Win + V keys to invoke the clipboard manager, you will see a prompt that says, “Can’t show history, See all copied items in place, Turn on clipboard history”. You have the option to turn it back on by simply clicking on the available button. Doing so would only hide the existing data and makes sure that no copy of the data is kept.

Conclusion

On the other hand, if you want to clear the clipboard without affecting its history data, you have to make sure to pin the items on the clipboard that you want to stay. After that, click on the three-dotted icon for the menu and click on the “clear all” option. This will delete all the entries but will keep the pinned items on your clipboard.

If you are facing a missing sechost.dll error in your Windows 10, welcome, you have come to the right place to solve it and get back your computer in working order. Sechost.dll is a file that allows other programs to function and complete their tasks as well as control and change the behavior of other programs. The file is found in Windows subfolder System32, it is a completely safe file and should not be deleted. Sometimes however various other reasons can corrupt it or delete it. This guide will lead you to common solutions on how to get file back up and running.

1. Update device driver

   Have you installed a new device and all of a sudden you get the error message that Sechost is missing? Update device driver, it is possible that the file has been corrupted or replaced with an older version and therefore reported as missing. Update device driver to lastest version and issue should run away.

2. Re-register file via command prompt

   If Sechost got corrupted re-registering will solve the issue, press ⊞ WINDOWS + X and choose Command prompt (administrator), click on it. type regsvr32 sechost.dll and press ENTER Reboot your PC

3. Reinstall application

   Usually, Sechost gone bad or missing is due to the installation of another application that corrupts the file. Reinstall the application to try to solve errors. In order to properly reinstall the application first use the control panel to remove it completely from the system and then install it again, hopefully, this time correct version of Sechost.dll will be installed in the system.

4. Check your hard drive

   In some cases, a hard drive malfunction can cause several files to be corrupted or gone missing. To eliminate hard drive malfunction run check disk from Windows on C drive to check it and find if there are any errors.

5. Uninstall Windows update

   Same as with some application, even Windows update could corrupt some files due to update not being properly downloaded. Try uninstalling the latest update and revert to the previous Windows state, then update it again.

The Volsnap.sys is a Windows operating system file that is related to the Volume Shadow Copy Service or VSS. It is known to cause a Blue Screen of Death error. The main cause of the Volsnap.sys Blue Screen errors include conflicts with the RAM, issues with the hard disk, incompatible firmware, corrupted drivers, malware infection, and many more. Despite its many possible causes, its fixes are quite straightforward so won’t have any problem following them. The Blue Screen errors that are related to the Volsnap.sys file are:

• KMODE EXCEPTION NOT HANDLED
• PAGE FAULT IN A NONPAGED AREA
• SYSTEM THREAD EXCEPTION NOT HANDLED
• IRQL NOT LESS OR EQUAL

You might want to try performing System Restore as it could resolve Blue Screen errors like the ones related to the Volsnap.sys before you proceed with the troubleshooting tips given below. To run System Restore, follow these steps:

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

If System Restore didn’t help in fixing the Blue Screen error, now’s the time for you to resort to the troubleshooting tips provided below but before you get started, make sure that you create a System Restore point first.

Option 1 – Check if the Volume Shadow Copy service is running and restart it

The first thing you need to do is check if the Volume Shadow Copy service. To do that, refer to the following steps:

• Click on Start and type “cmd” and right-click on Command Prompt from the search results.
• Then select the “Run as administrator” option to open Command Prompt with admin privileges.
• After that, type “net stop sdrsvc” and hit Enter to execute the command in stopping the Volume Shadow Copy service.
• Next, type the “net start sdrsvc” command and hit Enter to start the service again.

Note: You can also restart the service using the Windows Services Manager.

• In the Cortana search box, type “services” and click on the Services icon to open the Services Manager. Alternatively, you can also tap the Win + R keys to launch the Run prompt and then type “services.msc” in the field and hit Enter to open the Services Manager.
• From there, look for the Volume Shadow Service (sdrsv) from the list of services. Its Startup type should be set to Manual by default.
• Restart the service and if you don’t encounter any error while you turn it on, re-run the backup service and see if the backup process runs successfully.

Option 2 – Try checking the Memory for the Errors using Memory Diagnostic Tool

The Memory Diagnostic tool in windows can help resolve the Volsnap.sys Blue Screen error by checking and automatically fixing any memory-based issues. To run it, refer to these steps:

• Tap the Win + R keys to open Run and type mdsched.exe and hit Enter to open the Windows Memory Diagnostic Tool.
• After that, it will give two options such as:
  • Restart now and check for problems (Recommended)
  • Check for problems the next time I start my computer
• Once your computer has restarted, perform a basic scan or you could also go for the “Advanced” options such as “Test mix” or “Pass count”. Simply tap the F10 key to start the test.

Note: After you select your preferred option, your computer will restart and check for memory-based issues. If it finds any issues, it will automatically fix them and if there’s no issue found, then it’s most likely not a memory-based issue so you should try the other options given below.

Option 3 – Try to update or rollback your device drivers

If the first option didn’t work for you, then it’s time to either update or rollback the device drivers. It is most likely that after you updated your Windows computer that your driver also needs a refresh. On the other hand, if you have just updated your device drivers then you need to roll back the drivers to their previous versions. Whichever applies to you, refer to the steps below.

• Open the Devices Manager from the Win X Menu.
• Then go to the section of IDE ATA/ATAPI controllers as well as Storage Controllers and right-click on them to open the Properties.
• After that, switch to the Driver tab and click on the Uninstall Device button.
• Follow the screen option to completely uninstall it.
• Finally, restart your computer. It will just reinstall the device drivers automatically.

Note: You can install a dedicated driver on your computer in case you have it or you could also look for it directly from the website of the manufacturer.

Option 4 – Try to run the CHKDSK utility

Running the CHKDSK utility might also help you resolve the Volsnap.sys Blue Screen error. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 5 – Run the System File Checker Scan

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. 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.

• Restart your computer.

Option 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like Volsnap.sys. It can be found on the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

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.