Unregister vbscript.dll and jscript.dll from HKEY_CURRENT_USER to resolve this error:
1. Click on the Start menu, choose Run, type cmd and click OK
2. To unregister the VBScript engine, run this command: reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
3. To unregister the VBScript engine on a 64-bit OS, run this command: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
4. To unregister the JScript engine, run this command: reg delete "HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
5. To unregister the JScript engine on a 64-bit OS, run this command: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
So here you just need to do depending your OS version(32bit/64bit) you need to run the appropriate command.
Once I did that, my build started working as expected. I still do not know how this information ended up in HKEY_CURRENT_USER on my system, particularly because the same build worked correctly on the same machine a couple of days ago. However, I am now back into a state where I can build successfully, and I know of a possible workaround to try if I end up with similar build issues in the future.
Hope this information will everyone who face this issue...... :)
Happy learning.......................................
1. Click on the Start menu, choose Run, type cmd and click OK
2. To unregister the VBScript engine, run this command: reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
3. To unregister the VBScript engine on a 64-bit OS, run this command: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
4. To unregister the JScript engine, run this command: reg delete "HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
5. To unregister the JScript engine on a 64-bit OS, run this command: reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
So here you just need to do depending your OS version(32bit/64bit) you need to run the appropriate command.
Once I did that, my build started working as expected. I still do not know how this information ended up in HKEY_CURRENT_USER on my system, particularly because the same build worked correctly on the same machine a couple of days ago. However, I am now back into a state where I can build successfully, and I know of a possible workaround to try if I end up with similar build issues in the future.
Hope this information will everyone who face this issue...... :)
Happy learning.......................................
No comments:
Post a Comment