I have MW starting when Win7 64bit starts.As stated above,it only freezes sometimes with this message;
{Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (Exception from HRESULT: 0x80263001).
I close that box and another message to do with .Net framework comes up.
Any suggestions please.No problems with previous version.
MW 2010 1.0.19 sometimes freezes on startup
-
ru
Post
Fire me your logs to take a look, go Help >> Send Support Logs >> enter chris as the Ticket Number >> Send Logs...
Re: MW 2010 1.0.19 sometimes freezes on startup
harc99 wrote:I have MW starting when Win7 64bit starts.As stated above,it only freezes sometimes with this message;
{Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (Exception from HRESULT: 0x80263001).
I close that box and another message to do with .Net framework comes up.
Any suggestions please.No problems with previous version.
Fire me your logs to take a look, go Help >> Send Support Logs >> enter chris as the Ticket Number >> Send Logs...
-
ru
Post
Re: MW 2010 1.0.19 sometimes freezes on startup
Just to add, when you do this post a reply, in case the logs don't arrive for some reason.
- harc99
- Mystified Moa
- harc99
- Mystified Moa
Post
Re: MW 2010 1.0.19 sometimes freezes on startup
Latest thing, MW is starting up full screen even though I've selected it not to start with windows, and when starting to start minimized!!
-
ru
Post
Re: MW 2010 1.0.19 sometimes freezes on startup
You set it to start minimised in the MailWasher options or through the shortcut ? If the latter I don't believe MailWasher respects that setting. However it sounds like the settings didn't save properly, just go back, alter each of those options >> Save >> set them back >> Save...harc99 wrote:Latest thing, MW is starting up full screen even though I've selected it not to start with windows, and when starting to start minimized!!
- harc99
- Mystified Moa
Post
Re: MW 2010 1.0.19 sometimes freezes on startup
Don't you sleep!!!!!
Yep,set it in the program itself, and have done a save.Will try it on reboot.Thanks.
Yep,set it in the program itself, and have done a save.Will try it on reboot.Thanks.
-
ru
Post
but yeah, it was early afternoon before I dragged myself out of bed.....I have to get my 8 hours.
If I understand the error correctly that you sent, it means that the application thinks Desktop Composition (a feature of Aero) is disabled when it's not.
The first thing to try is see if there are any updated graphics drivers for your machine, depending on flavour you have, here are some links
http://www.nvidia.com/Download/index.aspx?lang=en-us
http://www.amd.com/us/Pages/AMDHomePage.aspx (right side pick boxes for desk, note and work)
http://www.intel.com/p/en_US/support?iid=hdr+support (US version) offers a detector and downloads.
http://www.matrox.com/graphics/en/support/drivers/
Re: MW 2010 1.0.19 sometimes freezes on startup
I live in NZ tooharc99 wrote:Don't you sleep!!!!!
Yep,set it in the program itself, and have done a save.Will try it on reboot.Thanks.

If I understand the error correctly that you sent, it means that the application thinks Desktop Composition (a feature of Aero) is disabled when it's not.
The first thing to try is see if there are any updated graphics drivers for your machine, depending on flavour you have, here are some links
http://www.nvidia.com/Download/index.aspx?lang=en-us
http://www.amd.com/us/Pages/AMDHomePage.aspx (right side pick boxes for desk, note and work)
http://www.intel.com/p/en_US/support?iid=hdr+support (US version) offers a detector and downloads.
http://www.matrox.com/graphics/en/support/drivers/
- harc99
- Mystified Moa
Post
Re: MW 2010 1.0.19 sometimes freezes on startup
Thanks for that Chris.Man, I hate updating the graphics drivers,always have.
Just updated to the latest and looks like that's fixed the problem.When MW started with Windows before, the screen would blink off and go to a solid looking taskbar then off and back to the translucent look.Now it stays translucent when MW starts up! Still does that- - goes to a solid taskbar--when Goldwave and a few other programs run.
If it plays up I'll let you know.
Thanks again.
Just updated to the latest and looks like that's fixed the problem.When MW started with Windows before, the screen would blink off and go to a solid looking taskbar then off and back to the translucent look.Now it stays translucent when MW starts up! Still does that- - goes to a solid taskbar--when Goldwave and a few other programs run.
If it plays up I'll let you know.
Thanks again.
-
ru
Post
Great. You'll notice that flicker, it seems to depend on the system just how noticeable it is. We'll add some more protection around the problem as well, so it means MailWasher won't crash though it would mean if MailWasher does encounter this issue it won't use Aero.
The problem is basically after MailWasher determines Aero is enabled, it's then told it's not and things start going south from there....I've seen other programs note the same at times, so perhaps there's an odd initialisation issue.
Re: MW 2010 1.0.19 sometimes freezes on startup
harc99 wrote:Thanks for that Chris.Man, I hate updating the graphics drivers,always have.
Just updated to the latest and looks like that's fixed the problem.When MW started with Windows before, the screen would blink off and go to a solid looking taskbar then off and back to the translucent look.Now it stays translucent when MW starts up! Still does that- - goes to a solid taskbar--when Goldwave and a few other programs run.
If it plays up I'll let you know.
Thanks again.
Great. You'll notice that flicker, it seems to depend on the system just how noticeable it is. We'll add some more protection around the problem as well, so it means MailWasher won't crash though it would mean if MailWasher does encounter this issue it won't use Aero.
The problem is basically after MailWasher determines Aero is enabled, it's then told it's not and things start going south from there....I've seen other programs note the same at times, so perhaps there's an odd initialisation issue.