Why extract language matters
People searching for spin the wheel often expect a direct exe button. GradXL49/DemoWheel tag v1.0 does not publish a standalone exe asset. The release body says to unzip and run the executable. Honest tickets prevent volunteers from hunting Softonic “fixes” when the real issue was a partial extract.
Inventory from the research unzip
Inside DemoWheel_release_v1.zip you should see release_v1/Demo Wheel.exe, release_v1/images/starfield.jpg, release_v1/README.md, and theme ini files under release_v1/themes/. Keep that whole tree together. Deleting themes breaks customization during spin the wheel sessions.
Step-by-step extract
Download the zip from the official v1.0 release. Right-click Extract All into a folder you keep, or use Expand-Archive in PowerShell. Open release_v1 and confirm Demo Wheel.exe is present before the first launch. Install walkthrough: /install-spin-the-wheel-windows.
Launch after extract
Double-click Demo Wheel.exe. If you script the launch, quote paths that include the space. Prove one SPIN click. First run: /spin-the-wheel-first-run.
Portable copies
Copy the entire release_v1 folder when you move to another Windows desk. Partial copies that omit images or themes create confusing tickets. Portable guide: /spin-the-wheel-portable-folder.
Soft parks and package managers
No winget or brew id was found. Do not invent extract-free package commands for macOS or Linux. Soft parks stay parked. Releases map: /spin-the-wheel-releases. Safe download: /spin-the-wheel-download-safe.
Common failure modes
Antivirus quarantine after a partial copy. Renaming the exe without updating the ticket. Extracting twice into nested folders until nobody knows which Demo Wheel.exe is official. Fix each case by returning to the same zip from GitHub Releases and extracting cleanly once for spin the wheel.
Ticket language you can reuse
Write one sentence: spin the wheel from GradXL49/DemoWheel tag v1.0 DemoWheel_release_v1.zip, extract all, run Demo Wheel.exe. That sentence beats vague download instructions that invite portal hopping. Add the folder path after the first successful spin so the next volunteer does not create a second copy in Downloads.
What to do when SmartScreen appears
Re-check that the browser address shows github.com/GradXL49/DemoWheel. Prefer the named zip over a mirror that promises a quieter install. Signing was UNVERIFIED on the research date, so honesty matters more than invented certificate claims. Download safety notes: /spin-the-wheel-download-safe. Safety overview: /is-spin-the-wheel-safe.
Classroom timing
Budget five minutes for download and extract on ordinary broadband, plus a few minutes to re-type titles. Theme art can wait until after the first SPIN works. First-hour checklist: /installed. Computer setup: /spin-the-wheel-for-this-computer.
Keeping adjacent tools separate
Wheel spinner, decision wheel, picker wheel, random picker, name picker, and raffle wheel searches belong on other doors. Mixing those installers into the same USB creates wrong-binary tickets. Keep this zip labeled for spin the wheel only.
After the room is calm
Bookmark Releases, retire Softonic shortcuts, and stop downloading alternate packs the same afternoon. Update later with a fresh zip when tags change: /update-uninstall-spin-the-wheel. Home pillar: /. GitHub overview: /spin-the-wheel-github. Releases map: /spin-the-wheel-releases.
Producer and streamer notes
If you spin live, rehearse once with the real title list before going on camera. Maximize the window and confirm text contrast on your capture card. Shadow text can hurt framerate on older laptops, so leave that option off during the show. Keep a browser picker tab as a cold backup only, labeled clearly so nobody “fixes” a blocked exe with a Softonic download mid-stream.
Family shared PCs
Write the Releases URL in the browser bookmark bar with a calm label. After vacation reimages, download DemoWheel_release_v1.zip again rather than restoring unknown Desktop shortcuts. Children should not need admin rights beyond the first extract for this portable spin the wheel path.
What success looks like
One documented folder, one proven SPIN, one Releases bookmark, zero mystery mirrors. That is enough for most desks. Anything else can wait until the next review date when assets change.
Extra install discipline for spin the wheel
Keep one Releases bookmark and one folder path. When a volunteer finds a faster mirror, compare the filename to DemoWheel_release_v1.zip before you allow it. If the mirror cannot show GitHub as the final hop, refuse it. That habit protects classrooms more than any slogan.
- One Releases URL on the ticket.
- One DemoWheel_release_v1.zip filename.
- One proven Demo Wheel.exe path.
Document soft parks explicitly on the ticket: macOS none, Linux none, winget none, brew none. Invented commands create false confidence and fail verification scripts. Upstream README already says Windows only for Demo Wheel.
When you teach spin the wheel, say the phrase people searched, then name Demo Wheel as the GPL-3.0 client that ships the zip. Phrase-first titles keep the head term ahead of the project name. Adjacent tools stay on other hosts so raffle and picker intents do not collide here.
After every successful event, resist downloading “better” packs the same night. Tomorrow is soon enough to evaluate a new tag. Until then, the reviewed zip remains the door. Related reading spans the releases page, the download-safe page, the GitHub overview, the installed checklist, and the home pillar for spin the wheel.
If antivirus quarantines Demo Wheel.exe, restore from the same official zip after you confirm the URL. Keep themes and images when you restore. Partial recoveries recreate missing-theme tickets. Portable copies should move the whole release_v1 tree, not a lone exe dragged to the Desktop.
Producers should store the title spreadsheet path beside the Releases URL. Re-typing titles is normal because the app has no CSV import on the reviewed build. Delete-and-add remains the Titles list workflow, and the last entry cannot be removed. Plan placeholders accordingly for spin the wheel shows.
Frequently asked questions
Is there a naked Demo Wheel.exe on Releases?
No. Tag v1.0 lists DemoWheel_release_v1.zip only. The executable lives inside the archive under release_v1/Demo Wheel.exe after you extract. Prefer DemoWheel_release_v1.zip from GradXL49/DemoWheel tag v1.0, extract Demo Wheel.exe, and keep Releases bookmarked for the next spin the wheel update on Windows.
Why does the exe name have a space?
Upstream ships the one-file build as Demo Wheel.exe with a space. Quote the path in PowerShell, or double-click from Explorer, when you launch spin the wheel. Prefer DemoWheel_release_v1.zip from GradXL49/DemoWheel tag v1.0, extract Demo Wheel.exe, and keep Releases bookmarked for the next spin the wheel update on Windows.
What else is in the zip?
Expect themes such as orange.ini and starfield.ini, images/starfield.jpg, and README.md beside the exe under release_v1 according to the research unzip inventory. Prefer DemoWheel_release_v1.zip from GradXL49/DemoWheel tag v1.0, extract Demo Wheel.exe, and keep Releases bookmarked for the next spin the wheel update on Windows.