• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1786
  • Last Modified:

ActiveX can't create object Scripting.FileSystemObject


I'm trying to run some .vbs scripts on my home PC (Windows XP Professional SP2).  They used to work great, but now when I run them I get the following error:

ActiveX component can't create object: 'Scripting.FileSystemObject'

Let me just say this is not a coding issue, I'm well versed in proper syntax, and this script has worked in the past.  I've also done a lot of research on the internet about this problem, here's what I've tried, and doesn't work.

- Reinstalled WSH 5.6
- ran regsvr32 scrrun.dll
- I've gone into the registry editor and ensured my account has permission to the COM object as well.

I'm out of ideas, I'm just about to reformat my PC to fix this problem, but I'd rather like to avoid this!  Can anyone suggest something that I may have missed?

1 Solution
Check whether there is any script blocking programme installed in your pc, for instance Script blocking for Norton AntiVirus, it blocked the script and treat it as a malicious. Disabled the script blocking and try
i've also notice some spyware blockers that may block something like this....one in particular that comes to mind is SpyBot.  Definately try disabling your AV and then run the script

Do a complete registry backup using ERUNT, and then use SubInACL to reset the registry permissions.


Take a complete registry backup using ERUNT:
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Chris DentPowerShell DeveloperCommented:

We get that on some of the PCs we use here for some reason. In some cases this MS Article has resolved the problem, but not in all cases:


Afraid I can't offer much beyond that, because I don't look after the PCs themselves I tend to just ask for them to be rebuilt if it's a persistant problem.

raterusAuthor Commented:
sramesh2k, as a last resort after looking at/trying the other comments here, I did this, it worked great to fix my problem.  I'm still not sure about what _else_ it may have done, but for now, this problem is fixed!
>> I'm still not sure about what _else_ it may have done

It resets the registry permission for the chosen hive, to defaults. Administrators and SYSTEM have full control over the keys. Nothing else should get affected.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now