Then find the 'Discord' folder in both of those windows, and delete it. If your OS tells you that the file cannot be deleted because it's still in use, open up the Task Manager and terminate all instances of Discord there and in the start up tab. Restart your system. Reinstall via Windows Download; In some cases, these extra steps may be necessary.
Related Articles
- 1 Rebuild a Print Spooler
- 2 Enable Printer Spooling
- 3 AVG Free Installation Failed at Start Service
- 4 Error Code 0x8004FF00 in Microsoft Security Essentials
Businesses frequently need to install application updates or upgrades or, in some cases, new programs. The Windows Installer Service is an integrated Windows function that allows you to install new applications or updates rather easily. However, if the service fails or becomes corrupted, setup program or installation routines that depend on it may fail to execute and install at all. When this happens, Windows usually displays a '1601,' '1603,' '1606' or '1719' error code for the failed installation - all are minor variants of the same general problem, though. Depending on the underlying problem, diagnosing or repairing a 1601 type installer error may be a relatively simple task -- or it could require a new installation of Windows.
Restart the Windows Installer Service
1.Click Start, type 'services.msc' (without quotes here and throughout) in the search box and press 'Enter.' The Services window appears on the screen.
2.Scroll down to the 'Windows Installer' entry in the Services list and double-click it. The Windows Installer Properties window appears.
3.Click the 'General' tab and then click the 'Start' button. Click 'Apply' and then 'OK.'
4.Attempt to install the application that caused the Windows 1601 or similar Installer Service error.
Reregister the Windows Installer Service
1.Click the Start butten, type 'cmd' in the search box and press 'Enter.' A new Command Prompt window appears.
2.Type 'msiexec /unregister' at the prompt and press 'Enter.'
3.Type 'msiexec /register' at the command prompt and press 'Enter.' Close the Command Prompt window.
4.Log out of Windows and restart the computer. Install the program that caused the Windows Installer service error.
Tip
- You can also perform a System Restore to attempt and correct Windows 1601 Installer Service errors. Enter 'System Restore' in the Start menu's search box and press 'Enter.' Select a restoration point when the computer was operating normally and not producing Windows Installer Service errors, then restore the system files and registry settings to that point in time. You will not lose any documents or other user-created files, but the process will uninstall any programs you added since the time and date of the restoration point.
Warning
- If the above methods do not resolve Windows 1601 errors, there is probably a registry error or corrupt file issue that common repair methods cannot repair; reinstalling Windows is probably your only reliable course of action for fixing the problem.
References (3)
About the Author
Jeff Grundy has been writing computer-related articles and tutorials since 1995. Since that time, Grundy has written many guides to using various applications that are published on numerous how-to and tutorial sites. Born and raised in South Georgia, Grundy holds a Master of Science degree in mathematics from the Georgia Institute of Technology.
Photo Credits
- cd on cd image by Stephen Kirkby from Fotolia.com
Choose Citation Style
Grundy, Jeff. 'How to Fix Windows Installer Error 1601.' Small Business - Chron.com, http://smallbusiness.chron.com/fix-windows-installer-error-1601-56981.html. Accessed 14 January 2020.
Grundy, Jeff. (n.d.). How to Fix Windows Installer Error 1601. Small Business - Chron.com. Retrieved from http://smallbusiness.chron.com/fix-windows-installer-error-1601-56981.html
Grundy, Jeff. 'How to Fix Windows Installer Error 1601' accessed January 14, 2020. http://smallbusiness.chron.com/fix-windows-installer-error-1601-56981.html
Note: Depending on which text editor you're pasting into, you might have to add the italics to the site name.
-->My last post was on CheckSUR and I wanted to follow it up with how you can use the CheckSUR utility to fix corruption errors that CheckSUR might detect, but that cant be fixed with the utility.
Typically, the way that CheckSUR works is that it takes the information included with its payload, loads it locally to your machine into the WindowsCheckSUR directory and then runs the actual executable on the system. As this executable runs, it detects discrepencies in the package store and corrects the errors that it carries a payload for. But, what do you do when you have a package manifest that shows up in the CheckSUR log but doesnt have the payload with it? If you were to call my team we'll typically try to walk you through getting the files from another server, taking ownership of the servicing directories and moving the files. But what if this is an isolated server? Worse, what if you only have one PC at home and you're having issues? Well, there is an easier way.
What you should do is identify the package(s) that CheckSUR was not able to fix, they're usually listed at the end of the log. From there, you can take that information and go the Microsoft Download site and pull down the KBXXXXXX.MSU that corresponds to the package that you're seeing failures on. Since you've already run CheckSUR to get to this point, you can copy that .MSU to the WindowsCheckSURpackages directory (NOTE: This directory does not exist by default and must be created) and then re-run CheckSUR which will take care of the rest. If you're still having issues afterwards, that just means that something else is going on with the system that is going to require more than CheckSUR can accomplish. Typically, this is true corruption and it may be unrecoverable.
As a side note, CheckSUR doesnt have a command line interface component, so you cant rerun it once its been downloaded and installed, you just need to re-run the downloaded MSU package.
![Windows installer download Windows installer download](/uploads/1/2/6/4/126477585/811186233.png)
Hope that helps.
--Joseph