AudionAudion
ENDERU

Audion Windows Tools by Max.mov

USER_GUIDE_EN.md

Audion Windows Tools by Max.mov

Contents

WPF interface for configuring Windows 11 after a clean install. It is an interactive companion-remix of Max.mov's guide, not a line-by-line visualizer. The app builds 13 sections from Manifests\Section##.psd1, renders action cards, and uses the shared Engine\TweakEngine.psm1 engine.

Microsoft recommendations and built-in Windows mechanisms have priority. official cards use documented sources from Microsoft, the hardware vendor, or the product author; Max.mov guide marks steps that definitely appear in the Max.mov guide; Max.mov approved is used only for a recommendation or implementation that was separately and explicitly approved; unofficial preserves alternative and experimental solutions without presenting them as the official path. See VIDEO_COMPANION_EN.md for the exact positioning relative to the video.

Quick Start

Double-click Start.exe in the project root. It is the single entry point: it resolves PowerShell itself and gives the window its own taskbar icon.

If Windows refuses to run the unsigned local executable, clear the block in the file's properties (right-click - Properties - Unblock). As a last resort the bundle carries Engine\Launch.bat, which resolves PowerShell the same way without the executable. It is a fallback, not a second way in.

PowerShell lookup order:

  1. Engine\PowerShell\pwsh.exe — bundled portable PowerShell 7.
  2. System pwsh.exe from PATH — fallback.
  3. Windows powershell.exe 5.1 — offline fallback for the first launch.
  4. For a fully portable toolkit, run Install\Install-Portable-PowerShell.cmd or use the in-app installation button.

App.ps1 relaunches itself in STA mode and elevated mode, imports the engine, loads all manifests, and opens the WPF window.

Engine\WindowIdentity.psm1 assigns the explicit WPF icon, small and large Win32 window icons, an AppUserModelID, and relaunch properties that point to Start.exe. This makes the taskbar show the application icon instead of the PowerShell process icon.

Interface Buttons

Card And Action Types

Manifest statistics: 13 sections, 69 subsections, 308 cards. Kinds: deeplink=64, docs=1, feature=1, link=118, manual=71, powerscheme=9, registry=10, script=33, service=1. Controls: button=217, checklist=71, toggle=20.

Project Layout

Audion Windows Tools by Max.mov/
├── Start.exe
├── App.ps1
├── CHANGELOG.md                    # version history
├── Assets/
│   ├── MaxMovLauncher.png / .ico  # source and multi-size launcher icon
│   ├── PowerSchemes/               # .pow files used by Section04
│   └── Scripts/                    # local PowerShell scripts
├── Engine/
│   ├── Launcher/                   # source and repeatable Start.exe build
│   ├── WindowIdentity.psm1         # window/taskbar icon and AppUserModelID
│   ├── TweakEngine.psm1
│   ├── MainWindow.xaml             # window markup
│   ├── Themes.psd1                 # interface themes
│   ├── Launch.bat                  # fallback start, if Windows blocks Start.exe
│   ├── Invoke-TweakProfile.ps1     # profile runner: the engine without a window, for agents
│   └── PowerShell/                 # portable PowerShell, created by installer
├── Skill/
│   ├── audion-windows-tools.skill  # AI-agent contract: what to do, what to ask about
│   └── Profiles/                   # curated card lists for the runner
├── Install/
│   └── Install-Portable-PowerShell.cmd
├── Manifests/
│   └── Section##.psd1
├── Strings/
│   ├── en.psd1
│   └── ru.psd1
├── Docs/
│   ├── README_RU.md / README_EN.md
│   ├── USER_GUIDE_RU.md / USER_GUIDE_EN.md
│   └── VIDEO_COMPANION_RU.md / VIDEO_COMPANION_EN.md
├── Tests/
│   └── Smoke.ps1                   # pre-release checks; the app never calls into this folder
├── Data/                           # portable state: backups, language, theme, panel layout
└── config/version.json

Complete Section And Function Map

Every section, subsection, and card is listed below. Each card includes id, action kind, control type, source, requirements, description, and the concrete action: URL/page opening, registry write, command/script call, power scheme import, service control, or manual checklist.

0. Windows Installation

10 subsections, 45 cards. Source: Manifests\Section00.psd1.

0.0 Data & Passwords

0.1 GPU Driver Preparation

0.2 Chipset & Network Drivers

0.3 Create Installation Media

0.4 Install Without USB (Optional)

0.5 Move Max.mov Archive to USB / Other Drive

0.6 BIOS Settings

0.7 Important Notes Before Installation

0.8 New Driver Install Method & MS Account Bypass

0.9 Start Installation

1. Driver Installation & System Update

6 subsections, 32 cards. Source: Manifests\Section01.psd1.

1.0 Setup Notes

1.1 System, Runtime & Reboot

1.2 NVIDIA Drivers

1.3 AMD Drivers

1.4 Intel Drivers

1.5 Wi-Fi & Network Drivers

2. Disk Preparation

4 subsections, 10 cards. Source: Manifests\Section02.psd1.

2.0 Partition Cleanup

2.1 Drive Letters & Explorer

2.2 User Folder Relocation

2.3 Apps & Gaming Folders

3. Browser Setup

4 subsections, 24 cards. Source: Manifests\Section03.psd1.

3.0 Install Browser

3.1 Edge Configuration

3.2 Edge — Tame It

3.3 Remove Edge (Optional)

Ordered workflow: bulk selection checkboxes are hidden so the step order cannot be broken. The footer button applies the next pending step from top to bottom; mark manual steps done only after completing the actual action.

4. Windows Settings

18 subsections, 89 cards. Source: Manifests\Section04.psd1.

4.0 Explorer Settings

4.1 System

4.2 Maintenance (Optional)

4.3 Power Scheme (Optional)

4.4 CTT Tweaker (Optional)

4.5 Devices

4.6 USB Power Management

4.7 SoundSwitch (Optional)

4.9 Disk Indexing (Optional)

4.10 Network & Internet

4.11 Personalization

4.12 More Personalization

4.13 Apps

4.14 Other Startup Settings (Optional)

4.15 Language & Time

4.16 Privacy

4.17 Windows Update

5. GPU & Monitor Settings

4 subsections, 16 cards. Source: Manifests\Section05.psd1.

5.0 Important Notes

5.1 Monitor Setup

5.2 Nvidia Settings

5.3 Official Nvidia Recommendations

6. Cooling Setup

1 subsections, 2 cards. Source: Manifests\Section06.psd1.

6.0 Cooling Setup

7. Steam & Game Launchers

2 subsections, 22 cards. Source: Manifests\Section07.psd1.

7.0 Game Launchers

7.1 Minecraft

8. Global Timer Resolution (Optional)

1 subsections, 2 cards. Source: Manifests\Section08.psd1.

8.0 Global Timer Resolution

9. FPS & Latency Testing

2 subsections, 6 cards. Source: Manifests\Section09.psd1.

9.0 Testing Notes

9.1 Testing Tools

11 subsections, 42 cards. Source: Manifests\Section10.psd1.

10.0 Community Resources

10.1 Browsers

10.2 System Utilities

10.3 File Management

10.4 Uninstallers

10.5 Security & Privacy

10.6 Media & Communication

10.7 Overclocking & Benchmarking

10.8 Audio

10.9 Gaming & Account Switching

10.10 Smartphone + PC Ecosystem

11. Mouse & Keyboard Settings

2 subsections, 3 cards. Source: Manifests\Section11.psd1.

11.0 Mouse Settings

11.1 Keyboard Settings

12. Max.mov Tweaks

4 subsections, 14 cards. Source: Manifests\Section12.psd1.

Local resources are stored in Assets\MaxMov. Old .reg, .bat, .cmd, .ps1, .exe, .lnk, .url, and executable archives from the donor pack are removed from resources so users cannot run or open them by accident.

12.0 Max.mov Hub

12.1 Profiles & Presets

12.2 Wallpapers, Cursors & Visuals

12.3 Gaming Pack

Operational Safety Reference

Treat every card according to its action type. An open action only navigates to a Windows page, folder, URL, or external utility. A script action may change system state. A manual checklist requires the operator to complete and verify the steps. Do not assume that opening a tool applies its recommended configuration.

Before disk, boot, registry, firmware, driver-removal, privacy, or security-policy changes, create a tested rollback path. Depending on the operation this may be a restore point, exported registry branch, driver package, BitLocker recovery key, system image, BIOS profile, or separate backup.

Use the sections as a dependency-aware sequence: establish Windows and recovery first, update chipset/network/storage/display drivers, verify disks, configure core Windows behavior, then tune browsers, GPU, monitor, cooling, games, input devices, and optional latency features. Benchmark before and after optional tweaks.

Do not apply several performance changes at once. A one-change-at-a-time approach makes instability, latency regression, or power/thermal problems reversible and measurable.

Driver And Update Review

Confirm hardware IDs and system model before installing a driver. Prefer the device or OEM source when it provides platform-specific packages. Create a recovery path before firmware or storage-controller updates. After installation, review Device Manager, Event Viewer, reboot requirements, and the actual driver version.

Avoid generic driver-removal or cleanup operations when the current package is needed for recovery, display output, network access, or storage boot.

Disk And Storage Review

Verify disk identity by model, serial, capacity, and existing partitions, not drive letter alone. Drive letters and removable-disk order may change. Back up data and recovery keys before initialization, conversion, partitioning, formatting, encryption, or destructive cleanup.

After storage changes, verify boot, BitLocker state, filesystem health, expected partitions, free space, and backup accessibility.

Display, GPU, And Cooling

Record the baseline resolution, refresh rate, color mode, GPU driver, temperatures, fan behavior, and stability. Apply display and performance changes separately. Confirm that the monitor is using the intended connection and refresh rate and that cooling remains safe under sustained load.

Overclocking, undervolting, fan curves, and power limits require measurement and a known reset path. A profile stable in a short benchmark may fail during long gaming or compute workloads.

FPS And Latency

Use consistent test scenes, background processes, power plans, and measurement tools. Compare averages, lows, frame-time consistency, input latency, temperature, clocks, and power rather than one peak FPS value.

Timer-resolution and latency tools are optional. Do not stack several tools or leave an undocumented background utility running. Confirm that changes are removed after reboot or Exit when that is the intended behavior.

Network, Browser, And Privacy

Review account, synchronization, proxy, DNS, certificate, extension, telemetry, and policy implications before applying a preset. Enterprise-managed devices may restore settings or reject local changes. Do not weaken browser or Windows security merely to remove a warning.

Recovery After A Problem

Stop applying new cards. Record the last change, symptoms, reboot state, and relevant logs. Use the narrowest rollback: restore the previous setting or driver before using a broad system restore. For boot or storage failures, use prepared recovery media and keys rather than improvised destructive commands.

Completion Checklist

Interface Map Maintenance

Treat the GUI map or manifest as the structured source for section order, card titles, controls, defaults, warnings, and action commands. This guide remains the human-readable layer: it explains prerequisites, risk, expected effect, verification, and rollback. When a card is added or renamed, update both layers so the interface, presentations, and operator training stay aligned.

A release review should verify that every visible action has a meaningful description and that dangerous operations identify elevation, reboot, service, driver, registry, disk, privacy, or network impact before execution. MaxMovGuide = $true records exact presence in the guide; add MaxMovApproved = $true only after separate explicit approval by Max.mov. Both fields affect card labels only, never execution.

All projects