Ok, I didn't understand your previous post.
Can you please re-test the development version I've sent you? Because that and the last debug build should be the same. Note that in your post about results of the "Development" version test, you have attached a debug log. But the development version does not produce any. Maybe I've misunderstood that post too.

Hello! Above I wrote that everything turned out there are no more errors. Thank you.

I do not see any "Cannot open file" errors in the log. Do you get this error or different one?

Hello! Happened! Now all the time gives the test.

I have emailed you a new debug build.

Hello! Used a new assembly of the library, running through the command line as indicated above. At the first start there were no errors, the word test appeared. But the second and subsequent runs result in the same zero error. I am attaching the log file.

Thanks.

I have added this issue to the tracker:
Issue 2163 – Workaround for using /ini=nul on systems when reading "nul" file fails

I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.

Sorry!

I need the winscpXXXXtrace.log. Thanks.

Ok, I'm attaching the log.

I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.

An error like this appears:

On the computers where the code fails, what happens if you run:

Hello! A problem when opening a session, and on some computers. When viewed in the debugger, I found that the error appears if HomePath throws an exception. If HomePath = "\" then everything is fine. Tell me what can be done? Attached is the debug log and a screenshot of the error.