Message251594
> Dependency Walker doesn't know how to resolve those DLLs on
> any platform - Win10 looks exactly the same.
On older systems the api-ms-win-crt-* DLLs should be physically installed in System32, so Dependency Walker should find them if they exist. For example, on a Windows 7 box:
>dir /b C:\Windows\System32\api-ms-win-crt*.dll
api-ms-win-crt-conio-l1-1-0.dll
api-ms-win-crt-convert-l1-1-0.dll
api-ms-win-crt-environment-l1-1-0.dll
api-ms-win-crt-filesystem-l1-1-0.dll
api-ms-win-crt-heap-l1-1-0.dll
api-ms-win-crt-locale-l1-1-0.dll
api-ms-win-crt-math-l1-1-0.dll
api-ms-win-crt-multibyte-l1-1-0.dll
api-ms-win-crt-private-l1-1-0.dll
api-ms-win-crt-process-l1-1-0.dll
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll
api-ms-win-crt-string-l1-1-0.dll
api-ms-win-crt-time-l1-1-0.dll
api-ms-win-crt-utility-l1-1-0.dll
In Windows 10 these DLLs are an API Set contract; they don't actually exist in the filesystem. For example, on Windows 10 GetModuleHandle for all of these DLLs returns a handle to ucrtbase.dll, whereas on Windows 7 each is a uniquely loaded module. |
|
Date |
User |
Action |
Args |
2015-09-25 18:38:59 | eryksun | set | recipients:
+ eryksun, paul.moore, tds333, tim.golden, zach.ware, steve.dower, acx01bc |
2015-09-25 18:38:58 | eryksun | set | messageid: <1443206338.99.0.909115974531.issue25223@psf.upfronthosting.co.za> |
2015-09-25 18:38:58 | eryksun | link | issue25223 messages |
2015-09-25 18:38:58 | eryksun | create | |
|