W10 to W11 inplace auto upgrade blocked

Hi,

If I want to install the inplace auto upgrade from W10 to W11, it is blocked by Sophos without any notification.
If I stop the HitmanPro.Alert service, the upgrade works.
My invocation is as follows:
setup.exe /auto upgrade /priority normal /noreboot /quiet /eula accept

Which exceptions do I need to define?

Best regards,
Thomas

  • After renaming hmpalert.sys, the inplace upgrade works.
    After renaming hmpalert.dll, the inplace upgrade works too.

    Best regards,
    Thomas

  • Hello Thomas,

    Thank you for reaching out to the community forum and sharing your fix for the said issue that you've encountered.

    I'm curious as to why it happens on your device, so I would like to ask what was the full version of your Windows 10 device that encountered this kind of issue? Are you only observing this to a specific device or multiple? If so? What are the OS versions as well for those devices that are facing the same issue with the one you've just upgraded to W11? 

    Glenn ArchieSeñas (GlennSen)
    Global Community Support Engineer

    The New Home of Sophos Support Videos!  Visit Sophos Techvids
  • Hello Glenn,

    the version is: W10 22H2 (Build 19045.3930)
    This happens on multiple devices!
    The version of the other device: W10 22H2 (Build 19045.3693)

    When I provide the W11 ISO and try to open the setup.exe by double-clicking, no window opens - it is being blocked by Sophos HitmanPro.Alert.

  • Hello Glenn,

    here is the setupact.log from the folder Panther with the error:

    2024-02-13 13:05:04, Info MOUPG SetupHost: Automation information initialized.
    2024-02-13 13:05:04, Info MOUPG SetupHost: Attempting to initialize OneSettings values
    2024-02-13 13:05:04, Info MOUPG OneSettings: Blocked by policy settings.
    2024-02-13 13:05:04, Error MOUPG CMoSetupOneSettingsHelperT<class CEmptyType>::GetSettingsParameters(210): Result = 0x8000000A
    2024-02-13 13:05:04, Info MOUPG SetupHost: OneSettings Initialized -> [No]
    2024-02-13 13:05:04, Info MOUPG SetupHost: Loading ID: [c7b6e4de-b741-42d8-ac05-16738c9e0bc5] from [C:\$WINDOWS.~BT\Sources\SetupMgr.dll]...
    2024-02-13 13:05:04, Error MOUPG CSetupHost::LoadSetupObject(2028): Result = 0x8007007F[gle=0x0000007f]
    2024-02-13 13:05:04, Error MOUPG CSetupHost::LoadSetupObject(2006): Result = 0x8007007F[gle=0x0000007f]
    2024-02-13 13:05:04, Error MOUPG CSetupHost::InitializeComponents(1746): Result = 0x8007007F[gle=0x0000007f]
    2024-02-13 13:05:04, Error MOUPG CSetupHost::Initialize(381): Result = 0x8007007F[gle=0x0000007f]
    2024-02-13 13:05:04, Error MOUPG CSetupHost::IsDiagnosticAnalysisEnabled(2774): Result = 0x8000000A[gle=0x0000007f]
    2024-02-13 13:05:04, Error MOUPG CSetupHost::ExecuteDiagnosticAnalysis(1590): Result = 0x8000000A[gle=0x0000007f]
    2024-02-13 13:05:04, Info MOUPG **************** SetupHost Logging End ****************

    ... after that I rename the hmpalert.dll to hmpalert.orig and the setupact.log looks good:

    2024-02-13 13:11:37, Info MOUPG SetupHost: Automation information initialized.
    2024-02-13 13:11:37, Info MOUPG SetupHost: Attempting to initialize OneSettings values
    2024-02-13 13:11:37, Info MOUPG OneSettings: Blocked by policy settings.
    2024-02-13 13:11:37, Error MOUPG CMoSetupOneSettingsHelperT<class CEmptyType>::GetSettingsParameters(210): Result = 0x8000000A
    2024-02-13 13:11:37, Info MOUPG SetupHost: OneSettings Initialized -> [No]
    2024-02-13 13:11:37, Info MOUPG SetupHost: Loading ID: [c7b6e4de-b741-42d8-ac05-16738c9e0bc5] from [C:\$WINDOWS.~BT\Sources\SetupMgr.dll]...
    2024-02-13 13:11:37, Info MOUPG SetupHost: Loading complete.
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: WorkingPath = [C:\$WINDOWS.~BT\Sources]
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: MediaPath = [\\Baramundi-01.lswdom.local\DIP$\OS\Win11_x64_23H2_neu]
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: InstallFilePath = [\\Baramundi-01.lswdom.local\DIP$\OS\Win11_x64_23H2_neu\Sources\Install.wim]
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: ActionListFilePath = []
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: Mode = [0x2]
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: Scenario = [0x1]
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: Product = [0x0]
    2024-02-13 13:11:37, Info MOUPG SetupManager::Initialize: Flags = [0x804]
    2024-02-13 13:11:37, Info MOUPG SetupManager: Working Directory: [C:\$WINDOWS.~BT\Sources]
    2024-02-13 13:11:37, Info MOUPG SetupManager: Local Media Path: [C:\$WINDOWS.~BT]
    2024-02-13 13:11:37, Info MOUPG SetupManager: Scratch Path: [C:\$WINDOWS.~BT\Sources\Panther]
    2024-02-13 13:11:37, Info MOUPG SetupManager: ESD Download Path: []
    2024-02-13 13:11:37, Info MOUPG SetupManager: Media Path: [\\Baramundi-01.lswdom.local\DIP$\OS\Win11_x64_23H2_neu]
    2024-02-13 13:11:37, Info MOUPG SetupManager: Drivers Path: [C:\$WINDOWS.~BT\Drivers]
    2024-02-13 13:11:37, Info MOUPG SetupManager: LangPacks Path: [C:\$WINDOWS.~BT\LangPacks]
    2024-02-13 13:11:37, Info MOUPG SetupManager: Install file found: [\\Baramundi-01.lswdom.local\DIP$\OS\Win11_x64_23H2_neu\Sources\Install.wim]


  • After deactivating the following setting, the in-place upgrade also works: