Saturday 2 July 2022

How to fix Windows Startup program errors (e.g. HP printer drivers/programs)

 After uninstalling some programs from your Windows system, you may find that as soon as you log in to your Windows account, you see some Windows dialog boxes which are reporting missing programs or DLL files, etc.



This is usually because the Uninstaller has forgotten to remove all of the programs or services that it had originally installed and configured to run on startup. There are two types of mechanisms which could be causing this:

                                        Files or Windows registry entries

First, make sure Windows File Explorer has the 'Show Hidden Items' checkbox ticked...

Next, log out of your Windows account and then log back in again. If the same problem re-appears, then you now have a quick and easy way to check if you have fixed the problem without needing to restart Windows each time.

Once you think that you have fixed the issue, Restart Windows (not shutdown but restart) to check that all is well before you delete the unwanted files or registry entries for good.

Warning: The following methods may harm your system if something goes wrong! Before using them, create a Restore Point (in Start Menu, search for 'Create Restore Point') so that you can undo any harm that you may inadvertently cause.

1. Check in Task Manager

Press Ctrl-Shift-Esc and click the Startup tab.

Now click on the Status column and check all the items that are  Enabled. If any look like they should not be there and may be causing the startup error, right-click on it and set it to Disable. You can also inspect the folder which contains the program. If you are sure that this program is the one causing startup errors you can always try temporarily renaming the folder and then rebooting to see if your error has gone away.

2. Remove programs from the Startup folders

Type shell:startup in Explorer (or a Run box invoked using WindowsKey+R) to see any user accounts startup items:





You can also type  shell:common startup to check for the startup items which affect all users (if any). Notice that Windows Explorer displays the folder as 'Start-up' for some strange reason but it is actually 'Startup' (good old Microsoft!).

Select any item which you think may be causing the problem, create a new folder called 'Junk' and move the suspect items into that folder. Then log out and back in again. If the problem is now fixed you can delete the 'Junk' folder (or just leave it there, just in case you later find that you need to restore one or more of the startup items).


3. Check Task Scheduler

Run the Task Scheduler and look for any items which you can disable.


4. Check Group Policy Editor

If you are using Windows Pro or Enterprise and you want to check applications which may run at startup, use the Group Policy Editor. Other Windows versions do not support this tool.

Press Windows + R keys and type gpedit.msc, click OK.





This will take you to the Group Policy Editor. In the left pane, go to User Configuration, where you select Windows Settings. Now, click on Scripts (Login / Logout), and in the right pane, double-click Login. In the Login Properties window, click the Add button, click the Browse button and select the application you want to run. After that, click Apply and OK to save your changes. After that, restart your computer and check if the application starts automatically with Windows or not.

5. Check the Registry

Press the Win+R key combination and type regedit and press Enter.

Browse to the following path:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run



Next, find the application that starts automatically when Windows starts up (in Control Panel - Programs and Features) and then remove it using right-click on the application and select the Uninstall option. 


If this fails,  first try renaming the executable that is pointed to by the Registry 'Run' key (or modify the Registry key itself so that the path is invalid and won't run). If that fixed the problem you can delete the registry Run entry and perhaps remove the entire program folder that it was pointing to.

Subscribe for more updates!

No comments:

Post a Comment