winfile do not work on windows pe 10

Question

winfile do not work on windows pe 10

snowdream opened this issue a year ago · comments

It crashed on windows pe 10:

VCRUNTIME140.dll Not Found、

I see:
Runtime:
Winfile.exe depends on the VS 2015 C++ runtime; you can download that from
https://www.microsoft.com/en-us/download/details.aspx?id=48145

Malcolm Smith · Answer 1 · Fri Apr 21 2023 01:17:34 GMT+0800 (China Standard Time)

It is expected that WinFile requires the Visual C++ runtime. I don't think that link is the right one though - download the latest from https://aka.ms/vcredist . After installing the runtime, does it still fail to launch?

snowdream · Answer 2 · Fri Apr 21 2023 12:03:17 GMT+0800 (China Standard Time)

I try to install vcredist on Win 10 PE,But failed.

vcredist can not be installed on Win 10 PE,

Chen (Kina) · Answer 3 · Sun May 07 2023 20:08:51 GMT+0800 (China Standard Time)

For your information, I had copied these files to the same folder of WinFile executable from my Win 10 installation, and WinFile seemed to be working normally in both Win 10 PE and Win 11 PE:

msvcp140.dll
vcruntime140.dll
vcruntime140_1.dll

(I know it may be discouraged, but sometimes having suitable tools running under PE is very comfortable.)

Malcolm Smith · Answer 4 · Mon May 08 2023 08:40:17 GMT+0800 (China Standard Time)

Oh, I fully understand why it'd be useful to have Winfile run on WinPE. What I don't know is the best way to support it. Normally Microsoft distributes software linked against the C runtime as a DLL, because doing so allows the DLL to be updated independently of the program. WinPE either wants to be statically linked with the runtime DLL, or possibly using an older compiler, to ensure the DLL is already there. Neither of these would be good to do except to support WinPE.

Good to know that it works by copying the DLLs though.

Chen (Kina) · Answer 5 · Wed May 24 2023 21:55:41 GMT+0800 (China Standard Time)

Oh, I fully understand why it'd be useful to have Winfile run on WinPE. What I don't know is the best way to support it. Normally Microsoft distributes software linked against the C runtime as a DLL, because doing so allows the DLL to be updated independently of the program. WinPE either wants to be statically linked with the runtime DLL, or possibly using an older compiler, to ensure the DLL is already there. Neither of these would be good to do except to support WinPE.

Good to know that it works by copying the DLLs though.

I think we can just assume, that a user who knows both WinPE and WinFile is an experienced DIYer who is willing to do these manual copy work and ensure runtime dependencies manually...

(Although WinPE and some homebrewed editions of it are somewhat "abused" widely by inexperienced users in my country now, for its simplicity and much smaller footprint than a full installation. By "abuse" I mean "beyond Microsoft's design")