Windows-Installation/Win11-Installation.md

@@ -146,7 +146,7 @@ To unpack you mast have zip or 7zip packages installed, using 7zip :
 
 ```
 cd /d D:\
-7z x <path_to_zip>\root_v6.34.06.win64.python311.vc17.relwithdebinfo.zip
+7z x <path_to_zip>\root_v6.38.00.win64.python311.vc17.relwithdebinfo.zip
 ```
 
 This will install 64 bit root version 6.34/06 to D:\root directory. But you can use any directory which you prefer. ROOT is installed in _relocatable_ mode.
@@ -234,17 +234,17 @@ You will see the output like this:
 
 ```
 -- Building for: Visual Studio 17 2022
--- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.26100.
--- The C compiler identification is MSVC 19.43.34810.0
--- The CXX compiler identification is MSVC 19.43.34810.0
+-- Selecting Windows SDK version 10.0.26100.0 to target Windows 10.0.26200.
+-- The C compiler identification is MSVC 19.44.35222.0
+-- The CXX compiler identification is MSVC 19.44.35222.0
 -- Detecting C compiler ABI info
 -- Detecting C compiler ABI info - done
--- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.43.34808/bin/Hostx64/x64/cl.exe - skipped
+-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/bin/Hostx64/x64/cl.exe - skipped
 -- Detecting C compile features
 -- Detecting C compile features - done
 -- Detecting CXX compiler ABI info
 -- Detecting CXX compiler ABI info - done
--- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.43.34808/bin/Hostx64/x64/cl.exe - skipped
+-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.44.35207/bin/Hostx64/x64/cl.exe - skipped
 -- Detecting CXX compile features
 -- Detecting CXX compile features - done
 -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
@@ -256,10 +256,11 @@ You will see the output like this:
 -- Found Threads: TRUE
 -- Found XercesC: D:/Xerces-C/lib/xerces-c_3.lib (found suitable version "3.3.0", minimum required is "3.3.0")
 -- Found OpenGL: opengl32
--- Found Geant4: D:/Geant4/11.3.2/lib/cmake/Geant4/Geant4Config.cmake (found version "11.3.2")
--- Configuring done (14.3s)
--- Generating done (0.1s)
--- Build files have been written to:  ... /B1-build
+-- Found Geant4: D:/Geant4/11.4.0/lib/cmake/Geant4/Geant4Config.cmake (found version "11.4.0")
+-- Configuring done (14.1s)
+-- Generating done (0.4s)
+-- Build files have been written to: .../B1-Build
+
 ```
 Now we can build and run example.
 
@@ -268,10 +269,10 @@ The build step:
 ```
 cmake --build . --config RelWithDebInfo --parallel 8
 
-Version MSBuild 17.13.19+0d9f5a35a pour .NET Framework
+Version MSBuild 17.14.40+3e7442088 pour .NET Framework
 
   1>Checking Build System
-  Building Custom Rule D:/Geant4/11.3.2/share/Geant4/examples/basic/B1/CMakeLists.txt
+  Building Custom Rule D:/Geant4/11.4.0/share/Geant4/examples/basic/B1/CMakeLists.txt
   exampleB1.cc
   ActionInitialization.cc
   DetectorConstruction.cc
@@ -280,9 +281,8 @@ Version MSBuild 17.13.19+0d9f5a35a pour .NET Framework
   RunAction.cc
   SteppingAction.cc
   Génération de code en cours...
-  exampleB1.vcxproj -> D:\workspace\GEANT4\installg4\install\MSVC\B1-build\RelWithDebInfo\exampleB1.exe
-  Building Custom Rule D:/Geant4/11.3.2/share/Geant4/examples/basic/B1/CMakeLists.txt
-
+  exampleB1.vcxproj -> D:\workspace\GEANT4\installg4\install\MSVC\B1-Build\RelWithDebInfo\exampleB1.exe
+  Building Custom Rule D:/Geant4/11.4.0/share/Geant4/examples/basic/B1/CMakeLists.txt
 ```
 
 To run exaple use command:
@@ -292,9 +292,11 @@ To run exaple use command:
 You will see the output like below:
 
 ```
+Available UI session types: [ Qt, Win32, csh ]
+
 **************************************************************
- Geant4 version Name: geant4-11-03-patch-01 [MT]   (21-March-2025)
-  << in Multi-threaded mode >> 
+ Geant4 version Name: geant4-11-04 [MT]   (5-December-2025)
+  << in Multi-threaded mode >>
                        Copyright : Geant4 Collaboration
                       References : NIM A 506 (2003), 250-303
                                  : IEEE-TNS 53 (2006), 270-278