Application loader error when installing

Hi guys,
I updated my bold last week and it launched an error when It got to the Documents to go update, so every time I try to use the app loader for installation or update this error comes up:

"the device does not have sufficient storage space to acccommodate your application selections. Please select fewer optional applications, or clear some application data from the device"

These are my memory specs:

Media Cart support: On
Encryption mode: None
Mass storage mode support: On
-----------------------------------
Application memory:
Fee:20.9mb
----------------------------
Device memory
Total: 859.2mb
Free: 858.7mb
-------------------------
Media Card
Total: 3.7Gb
Free: 3.1Gb

can anyone help me???

The same thing is happening to me. Never seen this before!

Have you found any info on why or how to fix this?

Originally Posted by hellion

Hi guys,
I updated my bold last week and it launched an error when It got to the Documents to go update, so every time I try to use the app loader for installation or update this error comes up:

"the device does not have sufficient storage space to acccommodate your application selections. Please select fewer optional applications, or clear some application data from the device"

These are my memory specs:

Media Cart support: On
Encryption mode: None
Mass storage mode support: On
-----------------------------------
Application memory:
Fee:20.9mb
----------------------------
Device memory
Total: 859.2mb
Free: 858.7mb
-------------------------
Media Card
Total: 3.7Gb
Free: 3.1Gb

That is new one for me too. I suspect the Applications Memory is the issue. 20+ Mb should be plenty.

Did it work correclty prior to the upgrade? If it not a carrier released upgrade, I would consider rolling it back to verify the problem is relate to the upgrade.

You can troubleshoot by using Applications Loader to temperoy remove applications until you are able to accomplish the install. Once that has been completed, re-install other applications.

Just tried upgrading from .151 to .167 and I got the same error. It never happened during any prior updates. Hope someone canfigure it out.