En nuestro departamento de desarrollo, los usuarios utilizan máquinas virtuales w2019. Estamos observando que cada día aparecen muchos archivos de caché nuevos .HTM en: C:\Users\iisuserpool\AppData\Local\Microsoft\Windows\INetCache\IE
Con este contenido:
<meta http-equiv="Content-Type" content="charset=unicode-1-1-utf-8"><!-- saved from url=(0015)assemblybinder: --><html><pre>
*** Assembly Binder Log Entry (***) ***
The operation was successful.
Bind result: hr = 0x0. The operation completed successfully.
Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Running under executable c:\windows\system32\inetsrv\w3wp.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: DisplayName = System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=
(Fully-specified)
LOG: Appbase = file:///D:/website/
LOG: Initial PrivatePath = D:\website\bin
LOG: Dynamic Base = C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\
LOG: Cache Base = C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\
LOG: AppName =
Calling assembly : *** Version=1.0.0.0, Culture=neutral, PublicKeyToken=null.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: D:\website\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=
LOG: Binding succeeds. Returns assembly from C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Design\v4.0_4.0.0.0__\System.Design.dll.
LOG: Assembly is loaded in default load context.
</pre></html>
¿Cómo podemos prevenirlo?
Gracias,