# Galaxy Book Enabler: running Samsung's Windows apps on a non-Samsung PC > Galaxy Book Enabler is a PowerShell installer that makes a Windows PC identify itself as a Samsung Galaxy Book so that Quick Share, Multi Control, Samsung Notes and the Galaxy Buds app can be installed and used. It is convenient and thorough, and it depends on Samsung's own packages plus a spoofed hardware profile, which is exactly where the risk sits. **Bananz0/GalaxyBookEnabler** — Enable Samsung Galaxy Book features (Quick Share, Multi Control, Samsung Notes, Galaxy Buds) on any Windows PC. Intelligent installer with 21 device profiles, package manager, Wi-Fi compatibility detection & automated setup. No hardware required. - Repository: https://github.com/Bananz0/GalaxyBookEnabler - Stars: 755 · Forks: 52 - Language: PowerShell - License: MIT - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/bananz0-galaxybookenabler ## What the tool actually does: a hardware identity change plus package installs Galaxy Book Enabler spoofs your Windows PC as a Samsung Galaxy Book, unlocking access to Samsung's ecosystem apps like Quick Share, Multi Control, Samsung Notes and more. The description is blunt about the mechanism, and the feature list confirms it: the automated startup behaviour is a registry spoof that runs on every boot. So there are two halves, and they carry different risk. The first half is identity. Windows reports a hardware model, and Samsung's app packages are gated on that model, so the installer makes the machine claim to be one of 21 Galaxy Book models, from the Book3, Book4 and Book5 families through Pro, Ultra and 360. The second half is the packages themselves, which are Samsung's own binaries, filtered into Core, Recommended, Full Experience or custom selections, with a package manager that can install or uninstall entire profiles with status tracking. The stated audience is someone on any Windows PC who wants the Samsung ecosystem apps, and the description says no hardware is required. The recent release tags are v3.1.5 from 2026-03-19, v3.1.0 from 2026-01-10 and v3.0.0 from 2025-12-05, so the 3.x line has been through a major version since December 2025. What the tool is not is a Samsung service. The apps are Samsung's, the support for them is Samsung's, and the compatibility is achieved by lying to the installer, not by any driver work. ## PowerShell 7 is a hard prerequisite, and winget is the first step The requirements section makes one thing non-negotiable: the script requires PowerShell 7.0 or later, because Windows ships with PowerShell 5.1 by default, which the readme states is not compatible. Installing it is a single command: ```powershell winget install Microsoft.PowerShell ``` There is a wrinkle the readme flags for people new to winget. If this is your first time using it, you may need to run winget list first to accept the source agreements, and the command may appear to stall without that step. That is a small detail that will otherwise cost an afternoon. After installing, the readme says to use pwsh (PowerShell 7) instead of powershell (Windows PowerShell 5.1). This matters for the whole workflow, because the installer uses native sudo for auto-elevation, and it is also the reason the scripts use modern PowerShell syntax throughout. Two other requirements are buried in the feature list rather than the requirements section, and they are easy to miss. Samsung MultiPoint Support, which lets Galaxy Buds connect to multiple devices through the Samsung Settings app, requires the SSSE patch and the Core package selection, which includes Samsung Settings, Settings Runtime and the Galaxy Buds app. And the System Support Engine, described as an optional experimental feature for enhanced Samsung integration, is Windows 11 only. ## Running the installer: locally first, and test mode before anything else The quick start section is direct about the order of operations. Best practice is to download Install-GalaxyBookEnabler.ps1 and run it locally from PowerShell 7, and the irm path is supported but local use is the preferred path. The one-line form downloads the script from the raw GitHub URL and pipes it straight into the shell: ```powershell irm https://raw.githubusercontent.com/Bananz0/GalaxyBookEnabler/main/Install-GalaxyBookEnabler.ps1 | iex ``` The safer form writes it to disk first: ```powershell irm https://raw.githubusercontent.com/Bananz0/GalaxyBookEnabler/main/Install-GalaxyBookEnabler.ps1 -OutFile .\Install-GalaxyBookEnabler.ps1 ``` and then you run it: ```powershell .\Install-GalaxyBookEnabler.ps1 ``` Piping a downloaded script into iex means you never see what you are about to execute with administrator rights. The two-step form lets you read the file, and for a script that edits the registry and installs system services, that difference is worth a minute. There is also a mode that makes no changes at all, and it is the first thing to use: ```powershell .\Install-GalaxyBookEnabler.ps1 -TestMode ``` Test mode simulates the entire installation without making any actual changes, and the readme describes it as a way to review what the installer will do before committing to it. The installer also requests administrator privileges by itself, so there is no need to run it as administrator manually, and the diagnostic logging is saved to %TEMP% and works even with the one-line install. ## Uninstall, Nuke Mode, and the granular removal options Removal is as thoughtfully documented as installation, and this is the part that should give you the most confidence in the project. There is a single-flag uninstall: ```powershell .\Install-GalaxyBookEnabler.ps1 -Uninstall ``` And when the installer is run against an existing installation, it offers granular options rather than one blunt reset. Reinstall is nuke plus fresh install, which completely removes everything while preserving the BIOS configuration, and then performs a clean installation. Uninstall everything removes all Samsung apps, services, scheduled tasks and configuration, with Nuke Mode as an option to delete all Samsung app data, including caches, settings and databases, during the uninstall. Uninstall apps only removes the installed Samsung apps while keeping services and scheduled tasks. Uninstall services only removes scheduled tasks and Samsung services while keeping the apps installed. That last distinction is a good sign about how the tool was designed. A user who wants the apps gone but keeps the hardware identity is a plausible case, and separating the two makes the tool usable in situations where a full wipe is unacceptable. The repository also documents a built-in Advanced Reset and Repair tool for fixing app issues, clearing caches and repairing permissions, and a Nuke Mode for a destructive uninstall that wipes all Samsung app data. The uninstall preserving BIOS config is worth noting, since the spoof itself touches system identity. ## Intel Wi-Fi adapters and what Quick Share cannot do The Wi-Fi compatibility check is the most useful piece of engineering in the tool, and it is the one that changes a purchase or deployment decision. The feature is described as automatically detecting Intel Wi-Fi adapters and warning about Quick Share limitations. Separately, a Multi Control Recovery Task restarts Samsung services at startup, five minutes after boot, with a one-minute grace period, to improve Multi Control and phone reconnection reliability. Those two features together say that on non-Samsung hardware the cross-device experience is approximate rather than native. The reason is visible in the project's topic tags, which include intel-wifi and intel-wireless-bluetooth. Samsung's Quick Share depends on specific wireless hardware capabilities, and the ecosystem apps assume a Samsung radio stack. The installer detects the adapter and warns you, which is the right thing to do, but a warning is not a fix. An Intel Wi-Fi user should expect Quick Share to be present and possibly degraded, and should treat the warning as a reason to check their own use case before installing. This is the clearest case where the tool is the wrong choice. If Quick Share transfers are the entire point, and your hardware cannot do them, no amount of spoofing changes that. ## Autonomous installs, the package profiles, and the documentation For CI or scripted use, the installer has a fully autonomous mode where every option is specified up front: ```powershell .\Install-GalaxyBookEnabler.ps1 -FullyAutonomous -AutonomousModel Book4Pro -AutonomousPackageProfile Recommended -AutonomousInstallSsse:$true -AutonomousSsseStrategy Dual -AutonomousConfirmPackages:$true -AutonomousCreateAiSelectShortcut:$false -DebugOutput -LogDirectory "C:\GalaxyBook\Logs" ``` The profile option supports Core, Recommended, RecommendedPlus, Full, Everything, Custom and Skip, and for Custom you pass package names or IDs with -AutonomousPackageNames. The model option accepts an exact model, and the readme documents the profile names used by the various Galaxy Book generations. The underlying install is a differential one, which skips already installed packages so re-runs are faster, and the installer has a package manager that can add or remove whole profiles from an existing installation with status tracking. Version management with update detection and migration support is included, and the readme mentions a differential install alongside a test mode. Documentation is split across several files, which is a good sign for a project of this kind. CHANGELOG.md, Explainer.md and PACKAGES.md sit next to the readme, and the readme links them as what is new, the explainer, and the package list. The repository also has a CONTRIBUTING.md and a tests directory, so the installer is covered by tests rather than being a single unreviewed script. ## Conclusion Galaxy Book Enabler fits a Windows user who wants Samsung's cross-device apps on a non-Samsung machine and is prepared to install Samsung packages and change the reported hardware profile. It does not fit a machine where changing the system identity is unacceptable, or a Quick Share user on Intel Wi-Fi hardware who expects the same transfer performance. Before running it, start with the -TestMode flag to see what the installer would change, install PowerShell 7 first, and read Explainer.md and PACKAGES.md to see exactly which packages are pulled in and what the spoof consists of. ## FAQ ### What does Galaxy Book Enabler do to my Windows PC? It spoofs the PC as one of 21 Samsung Galaxy Book models, including a registry spoof that runs at every boot, and installs Samsung's own app packages from the Galaxy Book series. The resulting apps include Quick Share, Multi Control, Samsung Notes and the Galaxy Buds app. ### What do I need before running the Galaxy Book Enabler installer? PowerShell 7.0 or later, which you install with winget install Microsoft.PowerShell, and you should run the script with pwsh rather than powershell. The readme notes that on first use of winget you may need to run winget list first to accept the source agreements. ### Can I see what the Galaxy Book Enabler installer would do before running it? Yes, there is a test mode. Running .\Install-GalaxyBookEnabler.ps1 -TestMode simulates the entire installation without making any actual changes, and the readme presents it as the way to review what will happen before committing. ### How do I remove the Samsung apps and the spoof again? Run .\Install-GalaxyBookEnabler.ps1 -Uninstall. On an existing installation you can choose between a full nuke and reinstall, uninstalling everything including services and scheduled tasks, uninstalling apps only, or uninstalling services only, with Nuke Mode available to delete all Samsung app data. ### Does Quick Share work on a PC with Intel Wi-Fi? The installer automatically detects Intel Wi-Fi adapters and warns about Quick Share limitations, so the feature is present but the transfer experience is not guaranteed to be native. Multipoint audio for seamless Galaxy Buds switching additionally requires the SSSE patch and the Core package profile. ## Sources - [Bananz0/GalaxyBookEnabler on GitHub](https://github.com/Bananz0/GalaxyBookEnabler) - [Issues](https://github.com/Bananz0/GalaxyBookEnabler/issues) - [License: MIT](https://github.com/Bananz0/GalaxyBookEnabler/blob/main/LICENSE) - [README](https://github.com/Bananz0/GalaxyBookEnabler/blob/main/README.md) - [Releases](https://github.com/Bananz0/GalaxyBookEnabler/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/bananz0-galaxybookenabler