I was WRONG - IconPackager DOES work on Win 11

I tested it again

I felt it necessary to correct my earlier post here that IconPackager did not work on Windows 11. That claim turned out to be completely erroneous.  First , a little background information. I had been having a disturbing issue with my desktop computer randomly shutting down for no apparent reason every single day. What I thought was surely a hardware issue , turned out to be a couple of faulty or incompatible software programs that I discovered by process of elimination. After uninstalling them and restoring my computer to it's full functionality ,  I began to wonder if these issues could have affected the proper function of other programs on my computer. My first thought jumped to the issue I had with IconPackager. I needed to do another test. I found , to my surprise , that IconPackager DOES actually work on Windows 11 despite the fact that Windows 11 at the present time does not use "live" folders. I tested it using a default Windows Vista package , A default Windows 7 package , and a few older custom packages from Wincustomize archives. There were only a couple that I tested that didn't display properly , but the majority of packages did apply and display properly. I am presently using IconPackager 10 on my Windows 11 machine and so far I have not had the issues that occurred when I first tested it. It seems to be working fine. I apologize for the false alarm on my original post and I hope Stardock will forgive me.

-- Ace --

66,016 views 12 replies
Reply #1 Top

Is nothing working or is it only the live folders that are not working?

Reply #2 Top

Quoting Neil, reply 1

Is nothing working or is it only the live folders that are not working?

There were several items that did not display properly , for instance , what was supposed to be a " recycle bin " icon displayed as a " document " icon. There were several mismatches like these,  as well as a few missing icons. Also , my screen went grey for almost 30 seconds while the system attempted to apply the changes. 

Reply #3 Top

I Forgot to mention that the control panel icons did not change when applying a new package. They remained the default Windows 11 icons.

Reply #4 Top

As a side note: Newest Insider Build -> Live Folders are back. ;-)

Reply #5 Top

Quoting c242, reply 4

As a side note: Newest Insider Build -> Live Folders are back. ;)

That's an interesting development

Reply #6 Top

What I'm most anxious to see is how "Package Building" capabilities will be impacted.

-- Ace --

Reply #7 Top

I do also believe that when building new packages , proper picture formats are going to be very important. I found that a few of my package creations that used larger picture formats did not display properly. Anything over 256x256 , likely won't display properly. That's just my personal hypothesis after having tested many packages.

-- Ace --

Reply #8 Top

I too was having some issues i could not lock down, my system is complex with 4 SSDs in a multi booting set up, i too thought Iconpackager was at fault as i was using IP 5, removed it and installed IP 10 and found it made my system even less stable than edition 5, i did spends a short while with no Iconpackager but then found what i thought may have been the issue, rectified that and installed IP5 again and it has been running fine too.

+1 Loading…
Reply #9 Top

Quoting naroon1, reply 8

I too was having some issues i could not lock down, my system is complex with 4 SSDs in a multi booting set up, i too thought Iconpackager was at fault as i was using IP 5, removed it and installed IP 10 and found it made my system even less stable than edition 5, i did spends a short while with no Iconpackager but then found what i thought may have been the issue, rectified that and installed IP5 again and it has been running fine too.

That's good to hear. I'm glad to hear that you also rectified the problem and that IconPackager is working well for you now. This all sounds very encouraging going forward. Hopefully it will be helpful to others that may also be experiencing issues with IconPackager.

-- Ace --

Reply #10 Top

Quoting AceMatrix, reply 9


Quoting naroon1,

I too was having some issues i could not lock down, my system is complex with 4 SSDs in a multi booting set up, i too thought Iconpackager was at fault as i was using IP 5, removed it and installed IP 10 and found it made my system even less stable than edition 5, i did spends a short while with no Iconpackager but then found what i thought may have been the issue, rectified that and installed IP5 again and it has been running fine too.



That's good to hear. I'm glad to hear that you also rectified the problem and that IconPackager is working well for you now. This all sounds very encouraging going forward. Hopefully it will be helpful to others that may also be experiencing issues with IconPackager.

-- Ace --

Hi Ace.

Just goes to show you how our set ups can vary hugely, i had more issues with the latest edition of Iconpackager 10 than i had with IP 5 on Windows 11. I was Gifted IP5 by my wife some years ago now and even though it should not be compatible with Win 11 it is still going strong.

Reply #11 Top

Please under no circumstances should you install IconPackager 5 on a modern 64 bit OS.

It WILL break your OS should you ever uninstall in a way that is unfixable easily.

IconPackager10 does not have this problem

Reply #12 Top

Quoting Neil, reply 11

Please under no circumstances should you install IconPackager 5 on a modern 64 bit OS.

It WILL break your OS should you ever uninstall in a way that is unfixable easily.

IconPackager10 does not have this problem

I know NB, it should not work but it does, IP 10 gave lots of issues with stability for me so removed it right away, tried out other icon changers and used them for a few weeks, then when i tied down my issue connected to a rogue theme, re installed IP5, i always make an Icon Recovery reg entry and use a dedicated uninstaller like IoBit. I have been using IP5 for every OS since XP, 64 bit included with no issues, i must be an enigma, but i take your advice, happily received, glad i made those extra precautions when i have uninstalled it in the past, maybe that is what saved me from the issues you describe.