Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> SaZ so and if to use the automatic assembly through windeployqt.exe, this problem will not be? (windeployqt.exe itself "" Qt5Core.dll?) SaZ>Qt5Core.dll it is not necessary and windeployqt it not . Application should without usage of absolute paths. It is logical. It is necessary to use qt.conf. SaZ> Esteem about . My question was - whether it is necessary for me to be perverted with qt.config (I do not want while needlessly to get into all these subtleties of adjustments of type of priorities of loadings and so forth) If I used windeployqt.exe (, on idea, should me make the automatic machine the correct assembly, that is if it is necessary, itself to add qt.conf or copied in a directory Qt5Core.dll, time in initial there "" the directory ) upd. , everything, the question is removed. windeployqt.exe, predictably, itself Qt5Core.dll The tool can be found in QTDIR/bin/windeployqt. It takes an.exe file or a directory that contains an.exe file as an argument, and scans the executable for dependencies. If a directory is passed with the - qmldir argument, windeployqt uses the qmlimportscanner tool to scan QML files inside the directory for QML import dependencies. Identified dependencies are then copied to the executable's directory. T he hardcoded local paths in Qt5Core.dll are furthermore replaced with relative ones.