IconPackages Can No Longer Recolor

When I was running Windows 10 and using IP, I found that it did not always apply the changes the first time I applied the them. I would have to go back and make the changes again an reapply, sometimes multiple times, but it would eventually apply correctly.

I am running the exact same Windows and IconPackager versions (Windows Home 22H2 19045.4780) (IP 10.03) and something similar is happening on my system. I can recolor packages, but first I get an error sound and this screen for a brief moment:

And sometimes (not always) this error message:

IconPackager has worked flawlessly until now, and I have not done any changes to my system, so I suspect this has something to do with last week's Windows update.

Is the issue appear on specific icon pack? I tested on my Windows 10 system an and for me recolor work. Do I need to do specific steps to reproduce the issue?

Thank you,

Basj,
Stardock Community Assistant

Happens with all iconpackages when I hit apply changes and not only when I try to recolor.

The uninstaller seems to be broken too. When clicking uninstall Stardock IconPackager, the default Windows icons are applied and the uninstaller is minimized to the taskbar "forever". I used Iobit uninstaller to remove IconPackager and rebooted and reinstalled, but no change. IconPackager changes the icons & recolors, but the system crashes (explorer restarts) every time.

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version from your account page. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.

Running the purge file, I get this:

That's not the correct path to where IconPackager is installed (should be C:\Program Files (x86)\Stardock\IconPackager). This box pops up 5-6 times when clicking ok, then the IconPackager wait screen appears and nothing more happens until I force a logout.

And yes, I was patient. Nothing happened for at least 5 minutes before I forced the logout.

I have as a test uninstalled and reinstalled several other apps now with no issues.

To eliminate the presence of viruses, I have done an online virus scan using Trend Micro's House Call with 0 threats found.

Please also check with the sfc /scannow and dism if needed.

Please try the following:

-For Win8/10 Users: Open the Start Screen, and type 'cmd'. Right-click on the search result and select 'Run as administrator' from below.

-For 7 Users: click Start, in the start search field type 'cmd'. Right-click on the search result and select 'Run as administrator'.

-Type: sfc /scannow

-Wait for the scan to complete (this can take several minutes)

Some help on how this looks should you need it:

https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

If the SFC finds errors, but cannot fix them, please also run the following command in the same command prompt window:

dism.exe /online /Cleanup-Image /RestoreHealth

Some help on how this looks should you need it:

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

The above command should assist with replacing any damaged or problematic system files. Please note, however, since it may require restoring certain files, this process can take some time and you will need to be patient until it has completed.

Please let me know whether this resolves your problem or if you have any additional questions.

 

Thank you,

Basj,
Stardock Community Assistant

No change.

You might have to uninstall IP manually.

Restart first, and then remove all the Stardock folders related to IP:

C:\Program Files (x86)\Stardock

C:\Users\pelai\AppData\Local\Stardock

C:\ProgramData\Stardock

I don't have it installed, so I can't remember if there is anything related to IP in the Documents folder

C:\Users\Your User Name\Documents

and then remove the IP folder in the Registry.

Computer\HKEY_CURRENT_USER\Software\Stardock

and then restart again.

Your packages are in C:\Users\Public\Documents\Stardock\IconPackager, so they should be safe.

Now you should be able to reinstall.

As I said earlier, that's not possible because the process crashes. (Reply #4) That's why I had to use Iobit uninstaller to remove it.

I did that.

There is not.

I did that too.

Yes.

I'm not or have not been unable to reinstall. Only uninstall using the standard procedure.

 

I think you might be right here.

As do I. When sfc and dism aren't enough to fix screwy problems, system restore is. This article discusses how to do a system restore without data loss.

What's nice about it is that it relates to recent problematic Windows updates. You can also try rolling back the latest update if the system restore option doesn't appeal to you.

It would appear that this effects the Home edition only as I have the same version IP, the only difference is that I am running Windows 10 Pro. I have tested IP and it is working flawlessly on my computer.

System restore has never given me anything but grief and have been disabled on every computer since many years. After several months with no issues, I decided to run Disk Cleanup tool on Friday and deleted everything from Windows updates to thumbnail cache and logs, so no rollback available either this time around. On the bright side, IconPackager changes icons and recolor for me (it just crashes and I have to reboot),  so I'll leave it at that for the moment.

I'll take another look at this with fresh eyes tomorrow. 

If so, you can run chkdsk /f /r  . Yrag swore by it.

Sure, if you have a faulty disk, but nothing wrong with my drives.

I don't have Home edition on my system. Can someone else with Home edition confirm this. Appreciate your feedback.

Thank you,

Basj,
Stardock Community Assistant

 

Avast says chkdsk cross-references the directory of files with the file system to verify that they match. During an MS (and other) updates, files get moved around. It's possible to get 'misplaced' so that IP or rather your 'puter can't find the right file and you get a crash. chkdsk by itself is just a diagnostic and doesn’t try to fix anything. chkdsk /f fixes any structural issues with the file system and directory, correcting inconsistencies between the two. If your drives are OK, without bad sectors, then certainly the /r isn't necessary.

There is this report regarding the last update, but I think the steps you've taken would have mitigated it: https://www.howtogeek.com/658194/windows-10s-new-update-is-deleting-peoples-files-again/

 

Just to show that it does work on the Pro edition of windows 10, I made this video. I do realize that it does not help those with problems who are using the Home edition, but it still might be good to know for troubleshooting purposes for any future updates.

Wow! I was not expecting so many replies. Thank you, everyone. It's nice to know I'm not the only one experiencing problems with IP. And it sounds like Jan is having way bigger problems with the application than I am. I think there might be something to what Jan said about the latest Windows update. Most of my packages apply properly, except a lot of the older ones, that don't have Live Folders. The package I was trying to recolor was "Squid", which always worked like a charm in the past. Even if I try to de-saturate the color or darken or lighten any package and apply it, the program doesn't make the changes and applies the theme with the default settings. Anyway, I guess I can live with that and if I want to change the color, I will just pick another package with close to the same colors I'm looking for.