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

    Fault : "Secure Boot isn't configured correctly" or Secure Boot Violation
    Fix   : Get the machine booting, then restore Secure Boot properly
    Source: https://jbtecwiz.com/support/win-sec-secure-boot

    Run as     : Firmware settings and WinRE
    Expect     : 45 minutes
    Risk       : medium
    Reversible : yes

    WHEN THIS IS THE RIGHT FIX
    It will not boot at all. Two stages: get in, then put the protection
    back.

    HOW TO UNDO IT
    mbr2gpt does not remove data, but take an image first. Secure Boot can
    be disabled again from the firmware.

    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.

    --------------------------------------------------------------------
    NO WARRANTY - USE AT YOUR OWN RISK

    This script is provided by JbTecWiz as-is and with no warranty of any
    kind, express or implied. You run it entirely at your own risk.

    JbTecWiz accepts no liability for any loss or damage arising from its
    use, including but not limited to data loss, downtime, or configuration
    changes that turn out to be wrong for your system.

    You are responsible for reading this script before running it, for
    satisfying yourself that it suits the machine in front of you, and for
    having a working backup first. Some steps cannot be undone.
    --------------------------------------------------------------------
#>

[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 '  "Secure Boot isn''t configured correctly" or Secure Boot Violation' -ForegroundColor White
Write-Host '  Get the machine booting, then restore Secure Boot properly' -ForegroundColor Cyan
Write-Host ''
Write-Host '  Risk: medium   Reversible   45 minutes'
Write-Host ''
Show-Prose 'No warranty. Use at your own risk - JbTecWiz accepts no liability. Read it before you run it, and have a backup.' 'DarkYellow'
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 'In the firmware settings, disable Secure Boot temporarily to establish whether that is genuinely the blocker. If it now boots, the diagnosis is confirmed.' -Manual

Invoke-Step -Number 2 -Do 'Establish which mode the disk is actually set up for.' -Why 'Secure Boot requires UEFI and a GPT disk. A machine cloned from an MBR/legacy install will never satisfy it, and no firmware setting fixes that -- the disk layout has to be converted.' -Command {
    $env:firmware_type
    Get-Disk | Format-Table Number,FriendlyName,PartitionStyle
}

Invoke-Step -Number 3 -Do 'If the disk is MBR and the machine is capable of UEFI, convert it in place.' -Command {
    cmd.exe /c 'mbr2gpt /validate /disk:0 /allowFullOS & mbr2gpt /convert /disk:0 /allowFullOS'
}

Invoke-Step -Number 4 -Do 'Switch the firmware to UEFI mode, disable CSM, then re-enable Secure Boot.' -Manual

Invoke-Step -Number 5 -Do 'If a dual-boot Linux install is involved, ensure it is using a signed shim rather than disabling Secure Boot permanently -- every current major distribution supports this.' -Manual

Write-Rule "  Confirm it worked"
Show-Prose 'The machine boots with Secure Boot on.' 'White'
Write-Host ''
if (-not $DryRun) {
    Confirm-SecureBootUEFI
}

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-sec-secure-boot' 'Yellow'
} else {
    Write-Host '  Finished.' -ForegroundColor Green
}
Write-Host ''
Show-Prose 'To undo: mbr2gpt does not remove data, but take an image first. Secure Boot can be disabled again from the firmware.' 'DarkGray'
Write-Rule