TI7 problem with desktop icons

Before running TI7:
http://home.deds.nl/~rogier/ti1.jpg

After making an image with TI7:
http://home.deds.nl/~rogier/ti2.jpg

The icons and their names changed to the windows defaults after making an image with TI7.

Restarting windows did NOT change them back to the state before running TI7.

Reapplying the (saved) windows theme did restore the icons, but they kept the windows default names

Only system restore or manual renaming got my icons back to the pre-TI7 state.

Can this be fixed in a future version?

Is there a workaround untill this is fixed?

 

Hi, 666

Welcome to Wilders and Acronis TrueImage Forums.

I do not understand what you mean by changing back to default.

Could you give us a bit more information please?

Take Care,
TheQuest

 

Looks like the server with the pics is offline sometimes.
Pics on another server, hope that makes things clear:


Before running TI7:

http://devil.members.easyspace.com/ti1.jpg

After making an image with TI7:

http://devil.members.easyspace.com/ti2.jpg

The icons and their names changed to the windows defaults after making an image with TI7.

Restarting windows did NOT change them back to the state before running TI7.

Reapplying the (saved) windows theme did restore the icons, but they kept the windows default names

Only system restore or manual renaming got my icons back to the pre-TI7 state.

Can this be fixed in a future version?

Is there a workaround untill this is fixed?

 

Hello 666,

I am having the same problem as well. The problem for some reason seems to only affect customizations to the icons listed in the Display Properties - Customize Desktop... applet of Windows XP (ie My Computer, My Documents, etc). Surely there has to be someone else out there that has experienced this same problem. If not, it would be nice if someone at Acronis would look into this and post a response here as to their findings.

Someone please respond and let us know why TI7 has this problem. Partly due to this issue, I reverted back to using TI6 Build350 as that version does not have this problem. I am hoping that Acronis will fix this issue in a future version.