Argument 'picture' must be a picture that can be used as a Icon


I'm trying to add an APP-V Application into SCCM and I get the following error message when it tries to read the manifest.xml.

Error : Argument 'picture' must be a picture that can be used as a Icon

Has anyone come across this at all and if so how did you get around it.


0 Comments   [ + ] Show comments

Answers (3)

Posted by: JMWebster 10 years ago
Orange Belt
The answer to this is that I’m trying to read a 16 bit icon file, as I Sequenced a 16 bit application.

If you replace the Icon file with a 32 bit one SCCM can read it and then import it ok.

Hope this helps someone.

Posted by: jnojr 10 years ago
Orange Belt
How the heck do you know if an icon is 16 bit or 32 bit? And if you have the wrong one, where do you get the right one?
Posted by: Rheuvel 10 years ago
Brown Belt
The sequencer extracts icons for every OSD from the source where the original shortcuts/executables point to. However, once in a while some formats are missing, especially with older (legacy/16-bit) apps. Not such a big deal.

There is 1 format however (I forgot which one it was) that makes SCCM go mad if it's missing.

Whenever I encouter this I found that the easiest solution was to use IcoFX (free tool) which has a button to generate all the missing icon formats that Windows might be using. So you're done with 1 click, save/replace the icon and you'll have a working SCCM import again.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ