Hello, and welcome to Sysnative!
I know you are going to hate me for saying this, but I don't want to open myself up for any potential problems in the future, so I've really got to. We have procedures here for the safe replacements of files. These include not only ensuring that we don't put the wrong file on the wrong computer, apply the wrong fix to the wrong user's computer, bungle the fix and leave the computer without the file, etc., but also cover security and infection control. There are multiple layers of security around Windows system files to prevent tampering or modification, and failing to put these all back correctly at the end of the fix can leave the system open to compromise by a single unscrupulous user. If we let it happen repeatedly and on enough systems, feasibly the user could automate the procedure and create a piece of malware from it. We must at all costs avoid this. Consequently, I cannot just provide you the file without also going through safe replacement procedures.
So, can you please provide me with the logfile which generated this result and I'll provide the file. Additionally, if you have already fiddled with the security around any of your Windows files, can you please tell me which as I would be more than happy to reset them for you as part of the same fix.
Thank you for your understanding.
Richard
