Desktop X Wrecked My Computer

Did you by any chance install Icon-packager as well? To my knowledge the recent releases of Desktop X didn't cause any system wide problems.

Where did you get your version of DesktopX? You show up as a visitor. Did you buy the whole ObjectDesktop suite or just DesktopX?

Do you mean DesktopX by itself? Not with any other programs?
The issues sound very similar to what earlier versions of IconPackager caused.

Here's a link to one of the latest posts Link

Here's an earlier post: .Link

I had issues with some programs running but not showing on my screen - deregistering the dll worked for me

Sounds like Windows script issue to me Link

Yes, I've had that too, and also shortly after I installed DX 3. Not sure if it's related or not. But anyway, it's an error with the Windows script engine. To fix, do the following:

You need to reregister Jscript.dll and Vbscript.dll

1. Click Start, and then click Run.
2. In the Open box, type regsvr32 jscript.dll, and then click OK.
3. Click OK.
4. Click Start, and then click Run.
5. In the Open box, type regsvr32 vbscript.dll, and then click OK.
6. Click OK.

Thanks a lot, it seemed to be a script issue. All I did for my computer to mess up was install Desktop X 3.1 off of this site. My friend did the same. But yea it's fixed, thanks!

I experience this last winter and didn't know it was caused by Stardock so I reinstalled Windows. Which was alright since the computer had accumulated a bunch of crud. Windows Blinds has worked fine since then, with the occasional DesktopX Widget as well. Cursor XP has also run fine. I haven't messed with IconX. Today I decided to load several widgets and this crash occured. Is there a program fix for this problem? I did the dll unregister and resolved it but it was an exciting couple of hours trying to load system restore, help, norton, find and then searching the net to find this post with the fix.

Nice one paxx, your script re-reg thing worked a treat. Norton Internet Security 2004 Professional, and the 2005 version, both experience problems after installed Object Desktop

Yes, it's a script issue with DesktopX and either NortonAntivirus or McAffee and their respective ScriptBlocking Tools.

The only solution I have found, short of reinstalling MSScript or re-registering scripts after EVERY boot was to disable ScriptBlocking in Norton.

I've emailed Stardock, but no replies.
Norton told me to just disable ScriptBlocking. I've done that, but now my computer is possibly not as safe as it once was, thanks to DesktopX.

Check These other posts as well.
https://www.wincustomize.com/Forums.aspx?ForumID=168&AID=83215#649639
https://www.wincustomize.com/Forums.aspx?ForumID=175&AID=41733#654244

I wish Stardock would figure out how to fix this pain in my rear.

Norton told me to just disable ScriptBlocking. I've done that, but now my computer is possibly not as safe as it once was, thanks to DesktopX....I wish Stardock would figure out how to fix this pain in my rear.

Some Stardock products (or items created with) use scripts. Norton blocks scripts.
The way I see it, the only way for Stardock to 'fix' that is not use scripts. Then the cool widgets and such won't work. I had Norton 2003 AV & PF for 2 yrs and had no problem. I run a product using script, I allowed it - Norton shut up. Take Norton off of auto and put on manual blocking - then you get options.

Or you could complain to Norton and have them revamp their script blocker. They're the one's blocking good script.

Norton told me to just disable ScriptBlocking.

That should tell you Norton doesn't think ScriptBlocking (or at least their version) is that important.

Some Stardock products (or items created with) use scripts. Norton blocks scripts. The way I see it, the only way for Stardock to 'fix' that is not use scripts.

But Norton doesn't block all scripts. Yes I agree, Norton should do something to help the problem, but it also seems to me since Norton doesn't block all scripts, that there appears to be something with DesktopX Scripts that Norton and McAfee find offensive. Couldn't Stardock and Norton figure out what the offense is and either have Stardock and/or Norton fix their product accordingly???

That should tell you Norton doesn't think ScriptBlocking (or at least their version) is that important.

It seems important to me. Is it not that important? What do you and others think?

I just read through this quickly and I have never experienced any of these problems with desktopX or IP..ive had other problems but none of the script type problems. My computer is an HP Pavilion and at least 5 years old. But....I got rid of Nortons long ago. Seems to be a conflict with certain antivirus programs and not just the Stardock product.

I use AVG ....I have not had to reformat in over 2 years...

I use AVG ....I have not had to reformat in over 2 years...

I use AVG also, and have never had a problem. Norton causes problems with everything. I don't even let it in the same room as my computer.

Trying to upgrade to NIS2005 caused my BITS to be destroyed and NIS never fully installed. I gave up after 5 days and switched to TrendMicro...have had no problems yet. Been almost 3 months.

AVG sounds good, but that doesn't help those who may be stuck with or forced to use Norton or McAffee.

The 2 yrs I had Norton - it was set to give a message about Scripts. Then I was allowed to choose to block always, run once, allow always. After 3 or 4 messages I hardly ever got a warning when running a product or creation from here. The mains ones that caused the warning were weather, and the script that remembers your desktop setup.

that there appears to be something with DesktopX Scripts that Norton and McAfee find offensive

I doubt very much whether Norton analyses the scripts to see whether they're 'offensive' or not. I've hardly used Norton since the DOS days but from other script-blockers I've seen, they just assume that anything with a .vbs, .js or whatever externsion is potentially harmful - only the user can really make the decision.

To me it sounds like Norton needs to be configured correctly to let you allow the scripts you know are OK.

If it is continually raising alarms over the same script that you allowed once before then there is a problem with Norton. If it is raising alarms for new scripts every time then that's a 'feature' you have to live with if you want to continue using Norton.

this is interesting, and if Norton Tech support wan't a bunch of automated robots i bet they would have figured this connection with NIS and desktopx months ago....

i too ran into this problem with my script engine and all java becomming currupted. but i did not attribute it to desktopx. i ended up uninstalling NIS 2004 and 2005 instead to fix my problem. if i had known it was desktopx fighting with norton i would have dropped desktopx first.

either way both stardock and norton need to address this issue... ive got 3 paperweight licenses of norton products and now i've bought pc cillin..when all i had to do in the first place was drop desktopx? this must get fixed!

When using norton's especially nis 2005 or 2004, if a program, widget or gadget seems to need the internet for it to work, a window usually pops up from norton's asking what do you want to do with choices. When your running desktop x with widgets or what ever else you are running, never use norton's default settings. I've never have had any problems with any scripting due to desktop x or norton's just by allowing each individual widget or gadget allowing it to use any settings. Plus since norton's runs from your browser settings you might want to check to see if you have script blocking settings up to high on your internet settings. Don't know if this helps anyone but I hope it does.

ive got 3 paperweight licenses of norton products .....when all i had to do in the first place was drop desktopx? this must get fixed!

why drop desktopx in favor of something that is bloated and a resource hog, destroys some vitals on uninstalling and is causing irritation? it doesn't even make your desktop pretty.

I'm sure if you send Norton an email they'll get right on it...oh, wait..I forgot...

if Norton Tech support wan't a bunch of automated robots i bet they would have figured this connection with NIS and desktopx months ago..

hmm... actually, it would be years ago. I had script warnings when I first used DTX 2 yrs ago.

I've never have had any problems with any scripting due to desktop x or norton's just by allowing each individual widget or gadget allowing it to use any settings.

what RockinMike said.