ItsMods

I got problems with genuine from windows, so i went searching and everytime i got the result of opening cmd and typing "slmgr -rearm" to fix my guine issue,
but everytime i get this error and after every fucking forum said re-register vbscript.dll it didn't work!!

So does anyone here on itsmods got a solution how to fix the error???

please respond asap, because i can't take all the fucking frustration anymore with fucking gay microsoft's genuine and gay vbscript bullshit (sorry for being mad)

Buy your Windows?

CScript Error: Can't find script engine "VBScript" for script "C:\Windows\system32\slmgr.vbs".

This was preventing the Software Licensing Service in Vista doing what it needs to - and consequently giving rise to the non-genuine message, despite a perfectly genuine install.

The conventional response is to re-register the dll using
regsvr32 vbscript.dll

This works fine in many instances - but in this case, although the registration gave rise to the 'succeeded' message, as it should (thereby showing that the dll was present), there was no change in the response from MGADiag.

Eventually, I got a clue to the problem from an obscure blog, which mentioned that some AV's blocked a particular registry entry, by substituting their own dll for the vbscript one.

The penny dropped at last - so I created a small reg file to put the default entry there instead.



and yes, it should also work in Windows 7 and XP

I don't know exactly how to utilize this code, but all i know is that it works.

(05-21-2012, 07:42)dylankrajewski Wrote: [ -> ]CScript Error: Can't find script engine "VBScript" for script "C:\Windows\system32\slmgr.vbs".

This was preventing the Software Licensing Service in Vista doing what it needs to - and consequently giving rise to the non-genuine message, despite a perfectly genuine install.

The conventional response is to re-register the dll using
regsvr32 vbscript.dll

This works fine in many instances - but in this case, although the registration gave rise to the 'succeeded' message, as it should (thereby showing that the dll was present), there was no change in the response from MGADiag.

Eventually, I got a clue to the problem from an obscure blog, which mentioned that some AV's blocked a particular registry entry, by substituting their own dll for the vbscript one.

The penny dropped at last - so I created a small reg file to put the default entry there instead.

Code:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
@="C:\\Windows\\system32\\vbscript.dll"
"ThreadingModel"="Both"

and yes, it should also work in Windows 7 and XP

I don't know exactly how to utilize this code, but all i know is that it works.

nice copy / paste, i already saw this exact post on other forums and as i mentioned, nothing worked for me so far

(05-21-2012, 07:42)dylankrajewski Wrote: [ -> ]CScript Error: Can't find script engine "VBScript" for script "C:\Windows\system32\slmgr.vbs".

This was preventing the Software Licensing Service in Vista doing what it needs to - and consequently giving rise to the non-genuine message, despite a perfectly genuine install.

The conventional response is to re-register the dll using
regsvr32 vbscript.dll

This works fine in many instances - but in this case, although the registration gave rise to the 'succeeded' message, as it should (thereby showing that the dll was present), there was no change in the response from MGADiag.

Eventually, I got a clue to the problem from an obscure blog, which mentioned that some AV's blocked a particular registry entry, by substituting their own dll for the vbscript one.

The penny dropped at last - so I created a small reg file to put the default entry there instead.

Code:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
@="C:\\Windows\\system32\\vbscript.dll"
"ThreadingModel"="Both"

and yes, it should also work in Windows 7 and XP

I don't know exactly how to utilize this code, but all i know is that it works.

how to use the code:
--- copy:

--- then paste into a text file
--- save the text file as test.reg
--- double click the text file and run it (UAC will ask you to confirm)


*** if their is an error that the changes have not been applied

--- run command prompt as administrator
--- type "regedit" and press enter
--- agree to the UAC window
--- search [ctrl + f] for "B54F3741" and locate the listing under "HKEY_CLASSES_ROOT\CLSID"
--- locate "InprocServer32"
--- check the default key
--- if set to anything but "C:\Windows\system32\vbscript.dll"
--- this is what will need to be changed

--- how to change this:
--- right click the "B54F3741-5B07-11cf-A4B0-00AA004A55E8" key -> left pane
--- select permissions, left click Administrators, click "Full" in the middle of the window to give Administrators group full permissions
--- close window
--- double click the test.reg file you created previously
--- you will then get a success message

--- NEXT

--- back to your "administrators" command prompt window [set in the windows\system32 directory]
--- type "regsvr32 vbscript.dll"
--- after success message
--- in command prompt window, type "sfc /scannow"
--- this will take a bit to run and verify, then download updates
--- when complete it will say that the changes will take affect after restart
--- restart computer

How to check if this worked

--- after restart, open notepad
--- copy: msgbox("Hello world")
--- save as hello.vbs
--- double click hello.vbs
--- you should now get a message box with --Hello world-- in it


Congrats!!! Vbscript should now be working on your computer

(02-19-2013, 11:44)greywolfe Wrote: [ -> ]

(05-21-2012, 07:42)dylankrajewski Wrote: [ -> ]CScript Error: Can't find script engine "VBScript" for script "C:\Windows\system32\slmgr.vbs".

This was preventing the Software Licensing Service in Vista doing what it needs to - and consequently giving rise to the non-genuine message, despite a perfectly genuine install.

The conventional response is to re-register the dll using
regsvr32 vbscript.dll

This works fine in many instances - but in this case, although the registration gave rise to the 'succeeded' message, as it should (thereby showing that the dll was present), there was no change in the response from MGADiag.

Eventually, I got a clue to the problem from an obscure blog, which mentioned that some AV's blocked a particular registry entry, by substituting their own dll for the vbscript one.

The penny dropped at last - so I created a small reg file to put the default entry there instead.

Code:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
@="C:\\Windows\\system32\\vbscript.dll"
"ThreadingModel"="Both"

and yes, it should also work in Windows 7 and XP

I don't know exactly how to utilize this code, but all i know is that it works.

how to use the code:
--- copy:

Code:

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32]
@="C:\\Windows\\system32\\vbscript.dll"
"ThreadingModel"="Both"

--- then paste into a text file
--- save the text file as test.reg
--- double click the text file and run it (UAC will ask you to confirm)


*** if their is an error that the changes have not been applied

--- run command prompt as administrator
--- type "regedit" and press enter
--- agree to the UAC window
--- search [ctrl + f] for "B54F3741" and locate the listing under "HKEY_CLASSES_ROOT\CLSID"
--- locate "InprocServer32"
--- check the default key
--- if set to anything but "C:\Windows\system32\vbscript.dll"
--- this is what will need to be changed

--- how to change this:
--- right click the "B54F3741-5B07-11cf-A4B0-00AA004A55E8" key -> left pane
--- select permissions, left click Administrators, click "Full" in the middle of the window to give Administrators group full permissions
--- close window
--- double click the test.reg file you created previously
--- you will then get a success message

--- NEXT

--- back to your "administrators" command prompt window [set in the windows\system32 directory]
--- type "regsvr32 vbscript.dll"
--- after success message
--- in command prompt window, type "sfc /scannow"
--- this will take a bit to run and verify, then download updates
--- when complete it will say that the changes will take affect after restart
--- restart computer

How to check if this worked

--- after restart, open notepad
--- copy: msgbox("Hello world")
--- save as hello.vbs
--- double click hello.vbs
--- you should now get a message box with --Hello world-- in it


Congrats!!! Vbscript should now be working on your computer

I just want to tell you I've been working on this problem for HOURS(many) and I am so grateful to you. This worked like a charm! You are a genius.

Best...

Gravedig..

EVER!