Window Blinds and Win7 Professional 64-Bit - severe problems

from WinCustomize Forums

I've moved this post to the Personal Computing > Windows 7 section

 

Hello there,

well, I know this is another win7 64-bit post ... but I've encountered severe problems with window blinds on my brand new (got it today) win 7 prof. 64-bit system.  Install via Impulse worked just fine, but after applying a blind ("frosted", and I chose the win7 style) some explorer file couldn't be read anymore and the system froze. After rebooting all I got was a grey screen and a cursor. No access to anything. I managed to restore my system using the "starting/start up assistance" (I shut down the system while booting to get access to the screen asking you how to start windows, offering the options "start windows normally" or using the "starting assistance" - sorry for my bad english, I don't know the correct english terms). But now I'm reluctant to even try using Icon Packager. Objekt Dock Plus seems to work, Cursor FX does work. My Virus-Scanner and Firewall (GData and Outpost Pro) are the same as on my XP-Notebook (32-bit) and neither has ever caused problems with any Object-Desktop application before and are running fine on my new system.

Is there a way to make WB etc. run on my sytem????

Thanks for any suggestions!

 

 

 

 

 

 

 

 

 

 

6,829 views 5 replies
Reply #1 from Stardock Forums Top

Hi Tintin,

I have a 32 bit system so may not be much help but I wonder if your security software could be blocking Windowblinds?  Some security suites have been known to cause issues although it sounds as though you've already covered that.  Still, I would make sure to white list the whole Window Blinds folder.   Explorer.exe and dwm.exe need to be able to run.  I am assuming you have aero enabled.  If nothing else works, you might try uninstalling Window Blinds and then reinstall it after a reboot.  Sorry I can't be more help.  Maybe some of the others will have some better ideas. 

 

 

Reply #2 from Stardock Forums Top

some explorer file couldn't be read anymore and the system froze.
End of quote

Any recollection of what this file was?

Offworld Trading Company
Reply #3 from WinCustomize Forums Top

Hallo Cameochi, hello Shirley,

thanks for your replies.

@Shirley: No, unfortunatly I can't recollect precisely what that file was. It was some Explorer-related file and the window displaying the message was Classic-Windows and not displayed properly as well. But I posted this in the win7 category as well and one user suggested that it might indicate a hard drive problem. Thus I will contact my vendor, and most likely will have to pack my tower, carry it there and we'll try to reproduce the problem.

@Cameochi: I used to run all my Stardock-Stuff on my 32-bit-XP-Notebook before and there I'm using the same Firewall/Anti-Virus-Program as on my new system. Everything worked fine. On my new system I can use Object Dock Pro and Cursor FX without any problems. Naturally I haven't tried about the other Object Desktop-Apps yet. But I might try to un install WB and reinstall it as you suggested.

Let's see what my vendor says...

Reply #4 from WinCustomize Forums Top

@ Shirley: 

I tried to apply a skin again (after un- and reinsatlling WB) and encountered the same problems - but now I noted down the error message (I've translated it as best as I could):

"the command in 0x002c000 is pointing to memory/repository 0xffffffff. Operation read couldn't be operated in memory/repository. Klick ok to exit the program."

This Message appears while the skin is being applied. At the same time all desktop icons and the windows taskbar disappear. I can exit WB by just normally clicking the exit button. Object Dock is still working but nothing else. And after reboot I get that blank screen.

System recovery fixed that. By the way Icon Packager is running without problems. So this really seems to be a WB-related problem...

Any suggestions appreciated, thanks!

Reply #5 from Stardock Forums Top

Time to contact support@stardock.com.  We'll need more specific info on your system.