[osgeo4w-dev] [osgeo4w] #804: Could not load qgis_app.dll - QGIS LTR 3.28.11 OSGeo4W Installer

[OSGeo4W]

#804: Could not load qgis_app.dll - QGIS LTR 3.28.11 OSGeo4W Installer
------------------------------------------------+--------------------------
Reporter:  ascottwwf                            |       Owner:  osgeo4w-
                                                |  dev@…
    Type:  defect                               |      Status:  new
Priority:  normal                               |   Component:  Installer
 Version:  1.0                                  |  Resolution:
Keywords:  QGIS LTR OSGeo4W scripted installer  |
------------------------------------------------+--------------------------
Comment (by ascottwwf):

 Replying to [comment:13 jef]:
 > Are you running this from the OSGEO4W-Shell?  Otherwise %OSGEO4W_ROOT%
 is not set.
 "OSGEO4W-Shell" - Sorry I'd not heard of that or how to run it, but I have
 now done some reading and understand, but realise this won't exist until
 the product is mainly installed

 Therefore unless the installer uses the OSGEO4W-Shell during the setup - I
 am not running it this way, this is being run during the PowerShell script
 install - See: [https://trac.osgeo.org/osgeo4w/ticket/804#comment:8]
 above, however I believe the qgis-ltr.bat gets executed towards the end of
 the installation - it's just it does not appear to run correctly on our
 Windows 10 machines (or our Windows 10 Sandboxes) - I notice your initial
 test was on a Windows 11 Sandbox (and you had used a slightly modified
 'Not strictly a Powershell' version of my script).

 I do have some concerns about the install - as good as it is, it does look
 heavily ported from Linux and in the logs there are quite a few forward
 slashes "{{{/}}}" in the paths to files which I am unsure if this is a
 logging issue or the actual command that is being run as you may know
 Windows has always used backslashes "{{{\}}}" to delineate between
 folders, so these commands may not work, I have also noticed some double
 backslashes "{{{\\}}}" in the logs too, so some paths written to the log
 have one or the other (not noticed any occurances of both combinations)
 e.g.

 1) {{{2023/11/20 15:05:03 running: cmd.exe /c "C:\Program
 Files\OSGeo4W_v2\\etc\postinstall\setup.bat"}}}

 2) {{{C:\Program Files\OSGeo4W_v2>textreplace -std -t
 apps/Python39/Scripts/f2py.exe}}}
-- 
Ticket URL: <https://trac.osgeo.org/osgeo4w/ticket/804#comment:14>
OSGeo4W <http://trac.osgeo.org/osgeo4w>
OSGeo4W is the Windows installer and package environment for the OSGeo stack.