I have to believe that the jscript.dll is corrupt. I ran sfc /scannow, and the log shows very much at the end that it is unable to repair the file.
I noticed the issue for two reasons:
1) Installing an update to NordVPN stopped the update without any display of an error. However, downloading the whole file and trying to install it ended in a short Windows error box saying an error occurred with jscript for customization. Then, uninstalling NordVPN and then reinstalling established the program again.
2) At startup MS Spotlight does no longer change the picture. Investigating this showed me that the folder C:\Users\myname\Appdata\Local\Packages\Microsoft.Windows.ContentDeliveryManager….\LocalState\Assets\ is empty.
I am not sure whether 2 has something to do with jscript.dll, but it could. In the result log of sfc the following line appears three times:
Cannot repair member file [l:11]’jscript.dll’ of Microsoft-Windows-Scripting-JScript, version 11.0.18362.592,
I waive on the complete line, but the remainder shows the probable folder like AMD64 and nonSxS.
The version of script.dll is 10.0.18362.592
I also ran DISM.exe /Online /Cleanup-Image /RestoreHealth
command from Windows PowerShell (administrator) environment with no result.
I checked the Event viewer and there are no significant Critical Errors in Event viewer, except for this one:
Event ID 10005 MSInstaller with this text: “Product: NordVPN — Error 2739. Could not access JScript run time for custom action .”
I also ran chkdsk c: /r /scan command. No problems found.
The PC runs ok except for the two things mentioned at the beginning. I do not want to rest the PC because of a single file failure. This file is a MS file!!!
Last but not least I tried to register the file again with regsvr32.exe jscript.dll, which ended up in a failure with some error message. I wonder what the real problem maybe. Something is broken somewhere.
I appreciate any advice but NO RESET because I lose all settings and apps and that may take weeks to recover to a status that is ok. To mention this the problem occured about 2 weeks ago.