This guide explains how to install CorePin, configure CPU profiles, assign optimization settings to games, and measure whether those changes actually helped.
CorePin is designed around a simple workflow:
Choose an optimization, assign it to a game, launch normally, and measure the result.
For detailed chart controls and metric explanations, see Performance Profiling. For benchmark methodology and score details, see System Benchmark. For help with a problem, see Troubleshooting.
- Getting Started
- Recommended First Setup
- CPU Profiles
- Game Library
- Assign Settings to a Game
- Understand Game Settings
- Temporarily Disable a Game Profile
- Verify the Correct Executable
- Launch Games Normally
- Measure Whether It Helped
- Benchmark Your PC
- Global Settings
- Updates and Maintenance
- Remove CorePin
- Getting Help
CorePin currently supports 64-bit Windows 10 and Windows 11. Automatic per-game optimization requires the CorePin service, but the desktop application does not need to remain open while you play.
Once a game has been configured, the service detects it when it starts, applies the saved settings, and restores temporary changes after the game exits.
- Download the latest release from the official release page.
- Extract the complete
.ziparchive to a normal Windows folder you control. - Keep the contents of the package together.
- Run
CorePin.UI.exe.
Do not move or delete individual files from the extracted package. The service, profiler, benchmark, updater, and notification helper are designed to run from the complete package.
Public CorePin binaries are not currently code-signed, so Microsoft Defender SmartScreen may warn that the publisher is unknown.
If you downloaded CorePin from the official release page and trust the package, select More info, then Run anyway. Do not disable SmartScreen globally just to run CorePin. Release packages also include checksums that can be used to verify the downloaded archive.
On first launch, CorePin prepares the Windows components used while a managed game is running. Approve the administrator prompts so CorePin can:
- create its power plans
- install the CorePin service
- start the service
You do not normally need to install or start the service manually. After setup, open Service and confirm that it shows Running and Versions match.
If you decline a prompt or setup cannot finish, use Install Service and Start on the Service page to complete setup later.
Administrator approval is required for operations that install, start, stop, update, or remove the service and for creating or removing CorePin power plans. Everyday profile and Game Library editing does not require the UI to run as administrator.
If the UI and service versions do not match, update or reinstall CorePin so both components come from the same release package.
Keep the first configuration simple:
- Confirm that the automatically installed service is running.
- Review the CPU profiles CorePin detected for your processor.
- Refresh the Game Library.
- Select one familiar game.
- Assign a sensible CPU profile.
- Leave Process Priority at Normal.
- Leave Enforcement off.
- Leave Core Isolation off.
- Launch and test the game normally.
- Add more advanced options one at a time.
- Record comparable sessions when you want to determine whether a change helped.
Change one major setting at a time. Changing affinity, priority, isolation, power behavior, and background optimization together makes it difficult to determine which change helped or hurt.
Open Core Pin Profiles. CorePin examines the processor topology and creates useful starting profiles where possible. Depending on the CPU, these can include layouts based on:
- V-Cache CCDs
- frequency-focused CCDs
- CPU cache groups
- Intel Performance and Efficiency cores
- one logical processor per physical core
- all available logical processors
A logical processor is one CPU thread exposed to Windows. On a processor with SMT or Hyper-Threading, one physical core normally provides two logical processors.
CorePin always provides a built-in All Cores profile. It includes every logical processor available to Windows and cannot be renamed or deleted.
Use All Cores when you want CorePin to manage other game settings without restricting the game to a smaller set of CPU cores.
| Profile | Typical Purpose |
|---|---|
| V-Cache CCD | Keeps a cache-sensitive game on the V-Cache chiplet. |
| Frequency CCD | Uses cores on the chiplet with the highest boost frequency. |
| Hybrid or Performance Cores | Favors Performance cores on a supported Intel hybrid CPU. |
| No SMT | Allows one logical processor per physical CPU core. |
| All Cores | Keeps all CPU cores available while CorePin manages the game. |
These are starting points, not guaranteed recommendations. Different games can prefer different layouts even on the same processor.
- Select the
+button. - Enter a unique and recognizable profile name.
- Select the logical processors the game may use.
- Use an available preset as a starting point if useful.
- Select Save.
At least one logical processor must remain selected. Profile tiles show the number of enabled logical processors and how many games use the profile. The trash button deletes a custom profile after confirmation; All Cores cannot be deleted.
The Save button remains muted when nothing has changed and turns orange while changes are pending. If you switch profiles, leave the page, delete the profile being edited, or close CorePin, you can save, discard, or cancel.
Open Game Library and select Refresh to scan supported providers. CorePin currently discovers locally installed games from:
- Steam
- Epic Games Store
- GOG Galaxy
- EA app
- Ubisoft Connect
- Battle.net
- Amazon Games App
- Meta PC VR
- Xbox app and Microsoft Store
Only games installed on the current PC are added. A title in a launcher or store account that is not installed locally will not normally appear. Keep the relevant launcher installed so CorePin can read its local library information and use the launch method expected by that provider.
Xbox discovery uses installed Windows game packages and Xbox gaming libraries. CorePin lists supported installed games, not every application in a Microsoft Store account. Amazon discovery reads the Amazon Games App's local installed game data and launch metadata.
If a game is not found automatically, it can usually be added manually.
The toolbar can be used to:
- search by title
- filter by provider or hidden status
- change sort order
- add a custom application
- refresh installed libraries
Use the + button for software that is not discovered automatically, including
portable games, DRM-free games, standalone simulators, utilities, and custom
applications.
Select the executable that actually runs the application. You can also set a working directory, launch arguments, and administrator launch behavior where required.
Adding an application manually does not copy or install it. CorePin stores the launch information and displays the entry under the Custom provider.
Open a game's ... menu and select Hide game. Hiding a title does not
delete its CorePin settings, assigned profile, or artwork.
Use the filter to display Hidden games, then select Unhide game to restore one.
Open a game's ... menu and select Edit artwork. You can choose a local
image, search for artwork, preview the selection, or restore the original
provider image.
From the Game Library:
- Hover over the game tile.
- Open its
...menu. - Select Edit profile.
- Choose a Core Pin Profile.
- Choose who should control CPU placement.
- Review process priority and isolation.
- Configure VR, launcher, power, or graphics options where applicable.
- Read the What will happen summary.
- Select Save.
The summary updates as settings change. It explains whether the selected CPU profile will be applied directly, kept as a fallback, or not applied because AMD and Windows own CPU placement. Unsupported options are disabled, and CorePin may warn about unusually restrictive combinations.
Saved changes take effect the next time the game starts. CorePin does not retroactively change the configuration of a game that is already running.
Scheduling Owner determines who controls the CPU cores used by the game.
| Mode | What Happens | Selected CorePin Profile |
|---|---|---|
| CorePin | CorePin explicitly manages CPU placement. | Applied directly. |
| AMD/Windows when active | AMD and Windows remain in control when their game placement engages. CorePin takes over when it does not. | Kept as CorePin's fallback. |
| AMD/Windows only | CorePin leaves CPU placement entirely to AMD and Windows. | Not applied. |
AMD/Windows modes are available only on supported systems. They are primarily relevant to supported dual-CCD AMD Ryzen processors using the appropriate AMD chipset software and Windows gaming features.
Choose CorePin for repeatable, explicitly selected placement. Choose AMD/Windows when active when you want automatic cooperation with AMD game scheduling and a CorePin fallback for games it does not recognize. Choose AMD/Windows only when you want CorePin to leave CPU placement untouched.
When AMD or Windows controls placement, the cores observed in a performance report may differ from the selected CorePin profile. That is expected.
Normal is the safest starting point. Higher priority may help some latency-sensitive games, but it can also delay audio, streaming, input, desktop, or background tasks. Treat High as a setting to test, not a universal improvement.
Enable Apply to children when the recognized process launches additional child processes that should receive the same settings. Leave it disabled when the real game executable is already matched directly.
Some games or third-party tools change process affinity or priority after startup. Enforcement periodically reapplies settings owned by CorePin.
Enable it only when there is evidence that a startup setting is not remaining in place. Enforcement does not override AMD/Windows-owned placement. With AMD/Windows when active, it matters only if CorePin takes over.
Core Isolation moves suitable background processes away from CPU cores reserved for the active game, then restores their previous affinities after the game exits.
| Mode | Recommended Use |
|---|---|
| Off | Recommended starting point. |
| Light | Conservative background separation. |
| Medium | Broader separation after Light has been tested. |
| Aggressive | Broadest isolation for deliberate comparison. |
CorePin avoids moving critical Windows components, anti-cheat software, CorePin itself, active game processes, and protected VR or system workloads.
Start with Off and confirm the game works normally before increasing the level. Stronger isolation is not automatically better.
Smart Background Optimization reduces the impact of suitable background activity while a managed game is running. It uses separate eligibility and safety rules rather than simply moving every process to another CPU set.
CorePin protects active games, configured applications, critical Windows components, anti-cheat processes, VR runtimes, and latency-sensitive workloads. Previous process state is restored afterward.
Use it as another setting to measure, not as an assumed improvement.
CorePin can apply configured power behavior while managed games are running. Depending on the detected hardware and selected settings, this can include CorePin-managed power plans. The previous Windows power state is restored after the last managed game exits.
Power behavior can affect responsiveness, boost behavior, energy use, heat, and fan noise. Compare both performance and side effects when testing it.
Enable VR Mode when supported SteamVR or OpenVR companion processes should participate in the game's temporary CPU-placement strategy. Relevant streaming and driver services remain protected.
For applicable games launched through CorePin, an OpenXR runtime can also be selected. CorePin restores the previous runtime after the game exits. If the user or another application changes the runtime while the game is running, CorePin preserves that newer selection.
Launcher cleanup can follow the global Service setting or use a per-game override. When enabled, CorePin may close eligible launcher processes after the game starts. Closed launchers are not automatically reopened after the game exits.
On a system with more than one graphics adapter, CorePin can ask Windows to prefer a selected GPU for a game. Driver settings, the game, Windows behavior, and hardware configuration can still influence the final adapter used.
The CPU badge on a game tile indicates that an assignment exists. Select the badge to disable or re-enable the assignment without deleting its saved settings.
- Blue: the assignment is enabled for future launches.
- Orange: the assignment remains saved, but Windows default scheduling is used for future launches.
Hover over the badge to see the current state. Remove assigned profile is different: it clears the saved association after confirmation.
Some launchers start helper processes before launching the real game. CorePin may ask you to confirm which process represents the game.
When prompted:
- Launch the game from the verification dialog.
- Wait until the real game reaches its main window or menu.
- Review the detected processes.
- Select the correct game executable.
- Confirm the selection and save Profile Settings.
If automatic detection does not find the correct executable, use Browse to select it manually.
For a launcher-discovered game, open Edit profile and select Change executable... at the bottom-left. You can keep the current executable, browse for another file, or launch the game and detect it again.
Save the changes and restart the game before testing the corrected configuration.
After configuration, CorePin does not require you to launch games from its Game Library. You can normally start one from its usual launcher, a desktop shortcut, the Windows Start menu, or CorePin itself.
The service detects the configured game process and applies the saved settings automatically.
CorePin's Play button is particularly useful for initial executable verification, custom launch arguments, manual entries, VR or OpenXR handling, and provider-specific activation. It is not required for ordinary profile application.
CorePin makes optimization measurable. A different CPU profile, priority, isolation level, or power setting does not automatically mean better performance.
A useful change may improve frame pacing, slow-frame performance, average FPS, temperatures, fan noise, CPU behavior, or background interference. It can also have no measurable effect or reduce performance.
- Record a normal baseline before changing anything.
- Keep the game version and graphics settings unchanged.
- Use the same save, route, scene, or built-in benchmark where possible.
- Change one major setting at a time.
- Let the system return to a similar temperature.
- Repeat each configuration more than once.
- Compare frame pacing and slow frames alongside average FPS.
The first launch after a game update, graphics-driver update, or shader-cache reset may perform extra setup and is often a poor baseline.
The CorePin service must be running.
- Open the game's
...menu. - Select Profile next game session.
- Confirm that the orange Profiler armed banner appears.
- Launch the game normally.
- Play the section you want to measure.
- Exit the game normally when finished.
Only the next matching launch is recorded. Cancel from the same menu or with the banner's close button. The banner clears when the game starts.
A CorePin CPU profile is not required, making it possible to record a Windows-managed run first and use it as a baseline.
The report is finalized when the game exits or when the configured duration or file-size limit is reached. Reaching a recording limit stops the recording, not the game.
Open Performance Reports and select a completed recording. CorePin summarizes the likely limiting component, CPU headroom, GPU behavior, memory pressure, storage behavior, and frame delivery from the measurements available on the system.
Expand Why this conclusion? to see the measurements behind a statement. Hardware-specific measurements are labeled unavailable when CorePin cannot obtain them; unavailable data is not treated as zero.
A complete recording can contain menus, loading screens, cutscenes, pauses, gameplay, and scene transitions. Drag across a chart to select representative gameplay. CorePin zooms into that range and recalculates the statistics and diagnosis. Use Full session to return to the complete recording.
Set a representative recording as the baseline, select another recording of the same game, and choose Compare. CorePin places the measurements side by side and highlights meaningful differences.
Use similar gameplay ranges from both sessions. Linked time ranges are useful when recordings follow the same route or built-in benchmark. A difference is evidence from those two runs, not a guarantee that every future session will behave identically.
See Performance Profiling for chart navigation, recorded metrics, CPU activity and affinity views, and detailed comparison guidance.
Open System Benchmark to measure the current PC without assigning a game profile or requiring the CorePin service.
- Quick Benchmark measures CPU simulation and DirectX 12 graphics.
- Full Benchmark adds DirectX 11 and ray-traced shadows when supported.
- Demo Mode runs the animated scene without measuring or storing a score.
On a PC with more than one graphics adapter, choose the adapter to test before starting. Completed results remain in local history. Mark a representative run as the baseline to compare driver, cooling, power, Windows, or hardware changes.
For repeatable testing, close demanding applications, keep driver and power settings consistent, and let the system reach a similar temperature. The benchmark is a repeatable gaming-style workload, not a prediction of FPS in a specific game.
See System Benchmark for Demo Mode options and detailed score explanations.
Open Service to configure settings that apply across games. Changes remain pending until you select Save. The button is muted when nothing has changed and turns orange while edits are pending. Ctrl+S also saves.
If you leave the page or close CorePin with pending changes, you can save, discard, or cancel.
Recommended (Auto) selects a suitable CorePin power mode for the detected processor. Other choices provide Windows-default, performance-oriented, and dual-CCD gaming behavior where supported.
CorePin restores the previous Windows power state after the last managed game exits.
Leave Low-Latency Mode disabled initially. Enable it only for a controlled test where you can compare performance, responsiveness, temperatures, power use, and background behavior.
CorePin can close its UI while a managed game is running to reduce desktop overhead. The service continues applying settings in the background.
CorePin can also close eligible launchers after a game starts. Closed launchers are not automatically reopened.
When enabled, Smart Background Optimization reduces the impact of suitable background activity during managed game sessions. CorePin automatically protects games, configured applications, latency-sensitive processes, anti-cheat and VR software, and critical Windows components. Previous process state is restored afterward.
This is a global feature; you do not need to maintain a process list for each game.
Choose maximum recording duration and file size. The first configured limit reached finalizes the report normally while the game continues running.
Enable Play sounds when recording starts and stops for brief confirmation when the UI is closed or hidden behind the game.
Select Remove CorePin system changes... in Service health to:
- stop the CorePin service
- uninstall the service
- remove CorePin-created power plans
The confirmation dialog lists the actions first. This does not delete the Game Library, CPU profiles, saved game assignments, benchmark history, or performance reports.
Use this action when you want to undo the Windows-level changes made during first-run setup without removing your CorePin data.
Open About for an overview of CorePin and service versions, processor information, CPU profiles, the Game Library, performance reports, and local data.
Select Check for Updates. When a newer release is available, the button changes to Download Update and then Install Update after the package is verified. CorePin attempts to preserve the service's previous running state during the update.
CorePin stores runtime data under:
C:\ProgramData\CorePin
This can include CPU profiles, game assignments, service configuration, library metadata, artwork selections and cache, benchmark history, and performance recordings. Most users should manage this through the UI rather than editing files manually.
The About page provides these actions:
- Copy copies the config or data-directory path.
- Open opens the CorePin data directory.
- Check integrity checks the local library database.
- Export creates a portable database copy.
- Compact reclaims unused database space.
Database exports can contain local game paths, provider metadata, and benchmark history. Review exported data before sharing it. Completed performance recordings are stored separately from the database.
Use Remove CorePin system changes... on the Service page when you want to uninstall the service and remove CorePin-created power plans while keeping your local CorePin configuration and data.
Run Remove-CorePin.cmd from the CorePin package. Approve the administrator
prompt and review the confirmation carefully.
Complete removal can delete the service, CorePin-created power plans, application files, configuration, Game Library data, cached artwork, benchmark history, and performance reports.
Run Remove-CorePin.cmd -WhatIf first to preview what would be removed.
Per-game Windows GPU preferences are intentionally left in place because
CorePin cannot reliably determine whether CorePin or the user originally
selected them.
See Troubleshooting for service setup, version mismatch, game discovery, executable matching, profile application, performance recording, benchmark, hardware-measurement, and recovery help.
CorePin is a personal, spare-time project rather than a commercially supported product. The documentation is the primary support resource. Questions, ideas, and bug reports are welcome, but responses, updates, and fixes are not guaranteed.
A useful report includes:
- CorePin and service versions
- Windows version
- CPU and GPU models
- game title and provider
- selected CPU profile and Scheduling Owner
- priority and Core Isolation mode when relevant
- the exact error message and clear reproduction steps
- a screenshot where useful
Include a performance report only when relevant and safe to share. Recordings can contain system information and local executable paths, so review them before posting publicly.
| Document | Purpose |
|---|---|
| README | CorePin overview, capabilities, and download information. |
| Performance Profiling | Detailed profiling, charts, recorded metrics, and comparisons. |
| System Benchmark | Benchmark modes, methodology, history, and scores. |
| Troubleshooting | Common problems and recovery procedures. |
| Security | Local trust model, service, elevation, network activity, and stored data. |
| Configuration | Advanced configuration information. |
| Documentation Index | Complete documentation map. |