#Requires -Version 5.1
<#
    JbTecWiz Support Centre -- generated fix script

    Fault : "Cannot start Microsoft Outlook. Cannot open the Outlook window"
    Fix   : Find the add-in that is failing at startup
    Source: https://jbtecwiz.com/support/win-office-outlook-wont-start

    Run as     : PowerShell as the affected user
    Expect     : 40 minutes
    Risk       : low
    Reversible : yes

    WHEN THIS IS THE RIGHT FIX
    Outlook starts in safe mode but not normally. Safe mode loads no
    add-ins, so this narrows it to one of them.

    HOW TO UNDO IT
    Re-tick any add-in you disabled. Nothing is removed by this process.

    This script walks the fix one step at a time and asks before each
    one. Steps with no command are things you do yourself -- it prints
    those and waits. Run with -DryRun to print without executing.
#>

[CmdletBinding()]
param(
    # Print every step and command without running anything.
    [switch]$DryRun,
    # Do not ask before each step. Read the script first if you use this.
    [switch]$Unattended
)

$ErrorActionPreference = 'Stop'
$script:Failed = 0

function Write-Rule { param([string]$Text)
    Write-Host ''
    Write-Host ('-' * 70) -ForegroundColor DarkGray
    if ($Text) { Write-Host $Text -ForegroundColor Cyan }
}

function Show-Prose { param([string]$Text, [string]$Colour = "Gray")
    if (-not $Text) { return }
    $words = $Text -split "\s+"; $line = "  "
    foreach ($w in $words) {
        if (($line.Length + $w.Length) -gt 74) { Write-Host $line -ForegroundColor $Colour; $line = "  " }
        $line += "$w "
    }
    if ($line.Trim()) { Write-Host $line -ForegroundColor $Colour }
}

function Invoke-Step {
    param(
        [int]$Number, [string]$Do, [string]$Why,
        [scriptblock]$Command, [switch]$Manual, [string]$Shell = "powershell"
    )
    Write-Rule "  Step $Number of 5"
    Show-Prose $Do "White"
    if ($Why) { Write-Host ""; Show-Prose $Why "DarkGray" }

    if ($Manual) {
        Write-Host ''
        Write-Host '  -> Do this yourself, then press Enter to carry on.' -ForegroundColor Yellow
        if (-not $Unattended -and -not $DryRun) { [void](Read-Host) }
        return
    }

    Write-Host ''
    foreach ($l in ($Command.ToString().Trim() -split "`n")) {
        Write-Host ("    " + $l.Trim()) -ForegroundColor Green
    }
    Write-Host ''

    if ($DryRun) { Write-Host "  (dry run -- not executed)" -ForegroundColor DarkGray; return }
    if (-not $Unattended) {
        $a = Read-Host "  Run this step? [Y]es / [S]kip / [Q]uit"
        if ($a -match "^[Qq]") { Write-Host "  Stopped at your request."; exit 0 }
        if ($a -match "^[Ss]") { Write-Host "  Skipped." -ForegroundColor DarkGray; return }
    }
    try { & $Command }
    catch {
        $script:Failed++
        Write-Host ("  Step $Number failed: " + $_.Exception.Message) -ForegroundColor Red
        Show-Prose "The rest of the fix may depend on this. Read the write-up before carrying on." "Red"
        if (-not $Unattended) {
            $c = Read-Host "  Carry on anyway? [y/N]"
            if ($c -notmatch "^[Yy]") { exit 1 }
        }
    }
}

Write-Rule
Write-Host '  "Cannot start Microsoft Outlook. Cannot open the Outlook window"' -ForegroundColor White
Write-Host '  Find the add-in that is failing at startup' -ForegroundColor Cyan
Write-Host ''
Write-Host '  Risk: low   Reversible   40 minutes'
Write-Rule

if (-not $Unattended -and -not $DryRun) {
    $go = Read-Host '  Ready? [y/N]'
    if ($go -notmatch "^[Yy]") { Write-Host "  Nothing was changed."; exit 0 }
}

Invoke-Step -Number 1 -Do 'Start Outlook in safe mode to get a working window.' -Command {
    cmd.exe /c 'outlook.exe /safe'
}

Invoke-Step -Number 2 -Do 'List what is registered to load, so you know what you are bisecting.' -Why 'LoadBehavior 3 means load at startup, 2 means loaded once and disabled after a failure, and 0 means off. An add-in sitting at 2 has already crashed Outlook at least once and is a strong suspect.' -Command {
    Get-ChildItem 'HKCU:\Software\Microsoft\Office\Outlook\Addins','HKLM:\SOFTWARE\Microsoft\Office\Outlook\Addins' -ErrorAction SilentlyContinue | ForEach-Object { [pscustomobject]@{ Addin = $_.PSChildName; LoadBehavior = (Get-ItemProperty $_.PSPath).LoadBehavior } }
}

Invoke-Step -Number 3 -Do 'In safe mode, go to File -> Options -> Add-ins -> Go, and clear every COM add-in. Restart normally to confirm Outlook now opens.' -Manual

Invoke-Step -Number 4 -Do 'Re-enable them one at a time, restarting between each, until the failure returns. The last one enabled is the culprit.' -Manual

Invoke-Step -Number 5 -Do 'Leave the culprit disabled and take it up with whoever supplies it. Update it before assuming it must stay off -- this is usually fixed in a later build.' -Manual

Write-Rule "  Confirm it worked"
Show-Prose 'Outlook starts normally with every add-in enabled except the one identified.' 'White'

Write-Rule
if ($script:Failed -gt 0) {
    Write-Host ("  Finished with " + $script:Failed + " failed step(s).") -ForegroundColor Yellow
    Show-Prose 'Read the full write-up at https://jbtecwiz.com/support/win-office-outlook-wont-start' 'Yellow'
} else {
    Write-Host '  Finished.' -ForegroundColor Green
}
Write-Host ''
Show-Prose 'To undo: Re-tick any add-in you disabled. Nothing is removed by this process.' 'DarkGray'
Write-Rule