Free, open-source Windows optimization tool for performance, privacy, and simplicity.
C# csharpdebloatdotnetgamingopen-sourceoptimizationoptimizeroptimizerduckperformanceprivacytweakertweakswindowswinui
feat(powerplan): bundle power plan and improve revert messaging
fatDuckfec055fff7d2
diff --git a/.github/.copilot-commit-message-instructions.md b/.github/.copilot-commit-message-instructions.mdnew file mode 100644index 0000000..793e203--- /dev/null+++ b/.github/.copilot-commit-message-instructions.md@@ -0,0 +1,42 @@+The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with [SemVer](http://semver.org), by describing the features, fixes, and breaking changes made in commit messages.++The commit message should be structured as follows:++```+<type>[optional scope]: <description>++[optional body]++[optional footer(s)]+```++The commit contains the following structural elements, to communicate intent to the consumers of your library:++1. **fix:** a commit of the *type* `fix` patches a bug in your codebase (this correlates with [`PATCH`](http://semver.org/#summary) in Semantic Versioning).+2. **feat:** a commit of the *type* `feat` introduces a new feature to the codebase (this correlates with [`MINOR`](http://semver.org/#summary) in Semantic Versioning).+3. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with [`MAJOR`](http://semver.org/#summary) in Semantic Versioning). A BREAKING CHANGE can be part of commits of any *type*.+4. *types* other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`, `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others.+5. *footers* other than `BREAKING CHANGE: <description>` may be provided and follow a convention similar to [git trailer format](https://git-scm.com/docs/git-interpret-trailers).++Additional types are not mandated by the Conventional Commits specification, and have no implicit effect in Semantic Versioning (unless they include a BREAKING CHANGE). A scope may be provided to a commit's type, to provide additional contextual information and is contained within parenthesis, e.g., `feat(parser): add ability to parse arrays`.++## Specification++The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt).++1. Commits MUST be prefixed with a type, which consists of a noun, `feat`, `fix`, etc., followed by the OPTIONAL scope, OPTIONAL `!`, and REQUIRED terminal colon and space.+2. The type `feat` MUST be used when a commit adds a new feature to your application or library.+3. The type `fix` MUST be used when a commit represents a bug fix for your application.+4. A scope MAY be provided after a type. A scope MUST consist of a noun describing a section of the codebase surrounded by parenthesis, e.g., `fix(parser):`+5. A description MUST immediately follow the colon and space after the type/scope prefix. The description is a short summary of the code changes, e.g., *fix: array parsing issue when multiple spaces were contained in string*.+6. A longer commit body MAY be provided after the short description, providing additional contextual information about the code changes. The body MUST begin one blank line after the description.+7. A commit body is free-form and MAY consist of any number of newline separated paragraphs.+8. One or more footers MAY be provided one blank line after the body. Each footer MUST consist of a word token, followed by either a `:<space>` or `<space>#` separator, followed by a string value (this is inspired by the [git trailer convention](https://git-scm.com/docs/git-interpret-trailers)).+9. A footer's token MUST use `-` in place of whitespace characters, e.g., `Acked-by` (this helps differentiate the footer section from a multi-paragraph body). An exception is made for `BREAKING CHANGE`, which MAY also be used as a token.+10. A footer's value MAY contain spaces and newlines, and parsing MUST terminate when the next valid footer token/separator pair is observed.+11. Breaking changes MUST be indicated in the type/scope prefix of a commit, or as an entry in the footer.+12. If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by a colon, space, and description, e.g., *BREAKING CHANGE: environment variables now take precedence over config files*.+13. If included in the type/scope prefix, breaking changes MUST be indicated by a `!` immediately before the `:`. If `!` is used, `BREAKING CHANGE:` MAY be omitted from the footer section, and the commit description SHALL be used to describe the breaking change.+14. Types other than `feat` and `fix` MAY be used in your commit messages, e.g., *docs: update ref docs.*+15. The units of information that make up Conventional Commits MUST NOT be treated as case sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.+16. BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.\ No newline at end of filediff --git a/.windsurf/workflows/generatechangelog.md b/.windsurf/workflows/generatechangelog.mdindex 292a0a5..d8b4e4c 100644--- a/.windsurf/workflows/generatechangelog.md+++ b/.windsurf/workflows/generatechangelog.md@@ -1,52 +1,101 @@-You are a professional software release writer.+You are writing release notes for a real software product used by real people.-Your task is to generate a clean, concise, and engaging changelog based on the provided working changes (git diff, file changes, or summaries).+Your job is not to summarize commits.+Your job is to understand the update and explain it in a way that feels useful, intentional, and human.-Step 1 — Understand the product:+The final changelog should feel like it was written by the developer of the product, not generated from git history.-- Infer what the project does based on the provided changes-- Identify the likely target users (e.g., developers, gamers, general users, etc.)-- Understand the purpose of the changes and their impact+You have access to the repository.-Step 2 — Write the changelog:+Explore the project yourself before writing:-Start with a short summary (1–2 sentences):+* inspect git diff+* inspect commit history+* inspect changed files+* inspect tags/releases+* inspect logs and summaries if available+* compare the latest release tag against the current state-- Describe the overall direction of this update-- Focus on user value and experience, not technical details-- Make it feel like a real product update, not a raw log+Do not rely only on commit titles.+Commit messages may be noisy, duplicated, experimental, misleading, or overly technical.-Then organize details into sections:+Focus on what actually changed for users.++Before writing:++* infer what the product does+* infer who the users are+* identify the overall theme of the release+* understand what users will notice or benefit from++Write release notes like a human developer.++The changelog should:++* feel natural+* feel intentional+* focus on user experience+* explain what feels better now+* avoid sounding robotic or corporate+* avoid sounding like commit messages++Do not expose raw implementation details unless absolutely necessary.++Ignore:++* formatting-only changes+* internal refactors without user impact+* temporary debug work+* low-value technical noise++Group related changes together into meaningful user-facing improvements.++Use this structure only when relevant:## New-- New features or capabilities that users can notice or use+New features or capabilities users can actively use.-## Fixes+## Changes-- Bug fixes, crashes, incorrect behaviors resolved+Behavior changes, redesigns, renamed functionality, or workflow adjustments.## Improvements-- Enhancements, optimizations, UI/UX refinements, performance upgrades+Polish, responsiveness, usability, reliability, clarity, UI/UX refinements, and quality-of-life improvements.++## Fixes++Bugs, incorrect behavior, regressions, crashes, failed operations, and edge cases that were resolved.++Writing rules:++* keep it concise but meaningful+* focus on user-visible impact+* explain why changes matter+* omit empty sections+* prefer clarity over hype+* avoid repetitive sentence structure+* avoid generic phrases like:++ * "Enhanced stability"+ * "Improved performance"+ * "Various fixes and improvements"+ * "Minor bug fixes"-Rules:+Instead of vague claims, explain what actually feels better.-- Be concise but meaningful-- Focus on user-facing impact (what changed for the user and why it matters)-- Do NOT mention file names unless absolutely necessary-- Do NOT include raw technical details (variables, code, diffs, logs)-- Merge related changes into clear, high-level bullet points-- Avoid generic wording like "minor fixes" unless nothing else is known-- Use natural, polished English (like real release notes from a product)+Examples:-Style guidelines:+* "Scrolling through large optimization lists now feels much smoother."+* "Error messages are clearer when an optimization fails to apply."+* "Applying changes is now more reliable when Windows blocks certain operations."-- Make the changelog feel intentional and purposeful-- Avoid robotic or repetitive phrasing-- Slightly emphasize improvements in usability, performance, or stability when relevant-- If the changes are small, still make them sound meaningful without exaggerating+Formatting rules:-Section rules:+* do not use em dashes+* prefer simple punctuation+* keep Markdown clean and readable+* avoid excessive bold text-- Omit any section that has no relevant items+The final result should read like authentic release notes from a polished software product update.diff --git a/AGENTS.md b/AGENTS.mdindex e76f516..6d1459d 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -1,43 +1,58 @@# Repository Guidelines-## Project Structure & Module Organization-- `optimizerDuck/`: main WPF app (`net10.0-windows`), organized by responsibility:- - `Domain/` for models/abstractions/attributes.- - `Services/` for system, optimization, feature, and configuration logic.- - `UI/` for XAML pages, dialogs, windows, controls, and ViewModels.- - `Resources/` for images and localization (`Resources/Languages/*.resx`).-- `optimizerDuck.Test/`: xUnit v3 unit tests, mirroring service/execution areas.-- `.github/`: CI, issue templates, PR template, and project policies.-- `publish.bat`: interactive/preset publish entry point (`Portable` or `Single`).--## Build, Test, and Development Commands-- **.NET Version**: 10.0.x (see `.github/workflows/ci.yml`)-- `dotnet restore optimizerDuck.slnx`: restore dependencies.-- `dotnet build optimizerDuck.slnx --configuration Release --no-restore`: CI-aligned build.-- `dotnet test optimizerDuck.Test/optimizerDuck.Test.csproj --configuration Release --no-build`: run unit tests.-- `dotnet run --project optimizerDuck/optimizerDuck.csproj`: run locally.-- `publish.bat portable` or `publish.bat single --skip-tests`: create release artifacts.--## Coding Style & Naming Conventions-- Use modern C# with nullable references enabled; prefer DI over direct service construction.-- Indentation: 4 spaces; keep formatting consistent with existing file-scoped namespace style.-- Naming:- - Types/methods/properties: `PascalCase`.- - Private fields: `_camelCase`.- - Locals/parameters: `camelCase`.-- Do not hardcode user-facing strings; add keys to `Translations.resx` and related locale files.--## Testing Guidelines-- Framework: xUnit v3 (`[Fact]` tests in `optimizerDuck.Test`).-- Name tests using behavior-focused patterns such as `ApplyAsync_Success_PersistsRevertDataFile`.-- Add/update tests for changes in `Services/`, optimization execution flow, and revert behavior.-- No explicit coverage gate is enforced in CI; prioritize meaningful unit coverage for changed logic.--## Commit & Pull Request Guidelines-- Follow Conventional Commits used in history: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `i18n:`, `chore:`.-- Branch from `master` (`feature/<name>` or `fix/<issue-id>`).-- PRs should include: clear description, linked issue (`Closes #123`), passing `dotnet build`/`dotnet test`, and screenshot/GIF for UI changes.--## Security & Configuration Tips+## Windows-Only WPF App+- **Windows-only**: Build/run/test only on Windows. Target framework: `net10.0-windows10.0.17763.0` with `UseWPF=true`. `CA1416` (platform compatibility) is silenced — all code is Windows-only.+- **Runs as admin**: `app.manifest` sets `requireAdministrator` UAC level.+- **Solution format**: `.slnx` (not `.sln`).++## Build, Test, Run Commands+- `dotnet restore optimizerDuck.slnx` — restore dependencies.+- `dotnet build optimizerDuck.slnx --configuration Release --no-restore` — CI-aligned build.+- `dotnet test optimizerDuck.Test/optimizerDuck.Test.csproj --configuration Release --no-build` — run all tests.+- `dotnet run --project optimizerDuck/optimizerDuck.csproj` — run locally.+- `publish.bat portable` or `publish.bat single --skip-tests` — create release artifacts.++## Project Structure+- `optimizerDuck/` — WPF app:+ - `Domain/` — models, interfaces, attributes (no UI deps)+ - `Services/` — business logic: `Configuration/`, `Features/`, `Optimization/`, `Revert/`, `System/`+ - `UI/` — XAML pages, ViewModels, windows, controls, dialogs, styles+ - `Common/` — extensions, helpers, converters+ - `Resources/` — images, embedded assets, localization (`Resources/Languages/Translations.resx`)+- `optimizerDuck.Test/` — xUnit v3 tests++## Optimization & Feature Discovery (Reflection, No Manual Registration)+- **New optimizations**: Create a **nested class** inside the relevant category class (e.g., `Domain/Optimizations/Categories/Performance.cs`), extend `BaseOptimization`, and decorate with `[Optimization(Id = "guid", Risk = ..., Tags = ...)]`.+- **New feature toggles**: Same nesting pattern inside `Domain/Features/Categories/`, extend `BaseFeature`, decorate with `[Feature(Section = ..., Icon = ..., Recommendation = ...)]`.+- **Category classes**: Must be decorated with `[OptimizationCategory(PageType = typeof(...))]` or `[FeatureCategory(PageType = typeof(...))]`.+- **Discovery**: `ReflectionHelper.FindImplementationsInLoadedAssemblies<T>()` scans all `optimizerDuck.*` assemblies — no DI registration array to update.+- **Static provider services**: `RegistryService`, `ServiceProcessService`, `ScheduledTaskService`, `ShellService` are **static classes** (not DI-registered). They capture revert steps into the ambient `ExecutionScope`.++## Revert System+- **File-based**: Each applied optimization creates `Shared.RevertDirectory/{optimizationId}.json`. Applied state is inferred from file presence on disk.+- **Atomic writes**: `RevertManager` writes to `.tmp` then `File.Replace` for crash safety.+- **Step types**: `RegistryRevertStep`, `ServiceRevertStep`, `ScheduledTaskRevertStep`, `ShellRevertStep`, `UsbPowerRevertStep`.+- **`ExecutionScope`**: Uses `AsyncLocal<ExecutionScope?>` for ambient step tracking — no need to pass context through parameters.++## Coding & Style+- Nullable enabled, file-scoped namespaces, implicit usings.+- Indent: 4 spaces. PascalCase types/members, `_camelCase` private fields, `camelCase` locals/params.+- **No hardcoded strings** — use `Translations.resx` keys. Access via `Loc.Instance["Key"]` or `Translations.KeyName`.+- **Keep comments sparse** — existing code has none; do not add them.+- DI via `Microsoft.Extensions.Hosting` + `CommunityToolkit.Mvvm`. Pages + ViewModels registered as singletons.+- Prefer `dotnet_diagnostic.CA1416.severity = silent` in `.editorconfig` (already set). Do not add `SupportedOSPlatform` guards.++## Testing (xUnit v3, Integration-Style)+- **No mocking libraries** — all test doubles are hand-written (`FakeOptimization`, `TestOptimization`, etc.) implementing interfaces directly.+- **Real I/O**: Tests use real filesystem (revert JSON files), real registry (`HKCU\Software\TestOptimizerDuck*`), real process execution (CMD/PowerShell).+- **STA thread**: Tests involving `ContentDialogService` or WPF components must use `RunInStaThreadAsync` helper (STA thread + `TaskCompletionSource`).+- **Logging**: Use `NullLogger<T>.Instance` / `NullLoggerFactory.Instance` for DI logging parameters.+- **Test naming**: `{Method}_{Scenario}_{ExpectedResult}` (e.g., `ApplyAsync_Success_PersistsRevertDataFile`).+- **Cleanup**: Use `try/finally` or `IDisposable` for test artifact cleanup (revert files, registry keys).+- **Coverage**: No coverage gate enforced — prioritize meaningful unit coverage for changed logic.++## Commit & PR+- Conventional Commits: `feat:`, `fix:`, `refactor:`, `docs:`, `test:`, `i18n:`, `chore:`.+- Branch from `master`: `feature/<name>` or `fix/<issue-id>`.+- PRs: clear description, linked issue (`Closes #123`), passing `dotnet build` + `dotnet test`, screenshot for UI changes.- Never commit secrets or machine-specific paths.-- For security issues, use private disclosure via `.github/SECURITY.md` guidance (not public issues).diff --git a/optimizerDuck.Test/optimizerDuck.Test.csproj b/optimizerDuck.Test/optimizerDuck.Test.csprojindex ae27618..d77f43a 100644--- a/optimizerDuck.Test/optimizerDuck.Test.csproj+++ b/optimizerDuck.Test/optimizerDuck.Test.csproj@@ -8,11 +8,11 @@</PropertyGroup><ItemGroup>- <PackageReference Include="coverlet.collector" Version="10.0.0">+ <PackageReference Include="coverlet.collector" Version="10.0.1"><PrivateAssets>all</PrivateAssets><IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets></PackageReference>- <PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="10.0.7" />+ <PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="10.0.8" /><PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.5.1" /><PackageReference Include="Newtonsoft.Json" Version="13.0.4" /><PackageReference Include="xunit.v3" Version="3.2.2" />diff --git a/optimizerDuck/Domain/Optimizations/Categories/PowerManagement.cs b/optimizerDuck/Domain/Optimizations/Categories/PowerManagement.csindex cbfcd9d..7face48 100644--- a/optimizerDuck/Domain/Optimizations/Categories/PowerManagement.cs+++ b/optimizerDuck/Domain/Optimizations/Categories/PowerManagement.cs@@ -1,4 +1,5 @@using System.Collections.ObjectModel;+using System.IO;using System.Text.RegularExpressions;using Microsoft.Extensions.Logging;using Newtonsoft.Json;@@ -142,7 +143,6 @@ public class PowerManagement : IOptimizationCategoryRisk = OptimizationRisk.Safe,Tags = OptimizationTags.Latency| OptimizationTags.Performance- | OptimizationTags.NetworkRequired| OptimizationTags.Power)]public class InstallOptimizerDuckPowerPlan : BaseOptimization@@ -168,28 +168,14 @@ public class PowerManagement : IOptimizationCategoryvar previousPlanGuid = match.Groups[1].Value;context.Logger.LogInformation("Current active power plan: {Guid}", previousPlanGuid);- progress?.Report(- new ProcessingProgress- {- Message = Loc.Instance[$"{ProgressPrefix}.Downloading"],- IsIndeterminate = true,- }- );-- var (success, powerPlanPath) = await context.StreamService.TryDownloadAsync(- Shared.PowerPlanUrl,- "optimizerDuck.pow"- );- if (!success || string.IsNullOrWhiteSpace(powerPlanPath))+ var powerPlanPath = Path.Combine(Shared.AssetsDirectory, "PowerPlans", "optimizerDuck.pow");+ if (!EmbeddedResourceHelper.TryExtract("PowerPlans.optimizerDuck.pow", powerPlanPath, true)){- context.Logger.LogError("Failed to download optimizerDuck power plan");- return ApplyResult.False(Loc.Instance[$"{ErrorPrefix}.DownloadFailed"]);+ context.Logger.LogError("Failed to extract embedded power plan");+ return ApplyResult.False("Failed to extract optimizerDuck power plan from resources.");}- context.Logger.LogInformation(- "Downloaded optimizerDuck power plan to {Path}",- powerPlanPath- );+ context.Logger.LogInformation("Extracted power plan to {Path}", powerPlanPath);progress?.Report(new ProcessingProgressdiff --git a/optimizerDuck/Domain/Revert/Steps/RegistryRevertStep.cs b/optimizerDuck/Domain/Revert/Steps/RegistryRevertStep.csindex 15f6c07..d022171 100644--- a/optimizerDuck/Domain/Revert/Steps/RegistryRevertStep.cs+++ b/optimizerDuck/Domain/Revert/Steps/RegistryRevertStep.cs@@ -77,7 +77,10 @@ public class RegistryRevertStep : IRevertStepTranslations.Revert_Registry_Description_RestoreKey,Path),- _ => $"Revert {Path}",+ _ => string.Format(+ Translations.Revert_Registry_Description_RevertUnknown,+ Path+ ),};/// <inheritdoc />diff --git a/optimizerDuck/Resources/Embedded/PowerPlans/optimizerDuck.pow b/optimizerDuck/Resources/Embedded/PowerPlans/optimizerDuck.pownew file mode 100644index 0000000..43bbdfbBinary files /dev/null and b/optimizerDuck/Resources/Embedded/PowerPlans/optimizerDuck.pow differdiff --git a/optimizerDuck/Resources/Languages/Translations.Designer.cs b/optimizerDuck/Resources/Languages/Translations.Designer.csindex 88000de..2964f44 100644--- a/optimizerDuck/Resources/Languages/Translations.Designer.cs+++ b/optimizerDuck/Resources/Languages/Translations.Designer.cs@@ -3024,15 +3024,6 @@ namespace optimizerDuck.Resources.Languages {}}- /// <summary>- /// Looks up a localized string similar to Failed to download optimizerDuck's power plan..- /// </summary>- internal static string Optimizer_PowerManagement_InstallOptimizerDuckPowerPlan_Error_DownloadFailed {- get {- return ResourceManager.GetString("Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Error.DownloadFailed", resourceCulture);- }- }-/// <summary>/// Looks up a localized string similar to Failed to import optimizerDuck's power plan../// </summary>@@ -3051,15 +3042,6 @@ namespace optimizerDuck.Resources.Languages {}}- /// <summary>- /// Looks up a localized string similar to Downloading power plan....- /// </summary>- internal static string Optimizer_PowerManagement_InstallOptimizerDuckPowerPlan_Progress_Downloading {- get {- return ResourceManager.GetString("Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Downloading", resourceCulture);- }- }-/// <summary>/// Looks up a localized string similar to Importing and activating power plan..../// </summary>@@ -3295,7 +3277,7 @@ namespace optimizerDuck.Resources.Languages {}/// <summary>- /// Looks up a localized string similar to Risky.+ /// Looks up a localized string similar to Expert./// </summary>internal static string Optimizer_UI_Risk_Risky {get {@@ -3764,6 +3746,15 @@ namespace optimizerDuck.Resources.Languages {}}+ /// <summary>+ /// Looks up a localized string similar to Revert registry: {0}.+ /// </summary>+ internal static string Revert_Registry_Description_RevertUnknown {+ get {+ return ResourceManager.GetString("Revert.Registry.Description.RevertUnknown", resourceCulture);+ }+ }+/// <summary>/// Looks up a localized string similar to Disable scheduled task: {0}./// </summary>diff --git a/optimizerDuck/Resources/Languages/Translations.resx b/optimizerDuck/Resources/Languages/Translations.resxindex 11419ad..5ab11da 100644--- a/optimizerDuck/Resources/Languages/Translations.resx+++ b/optimizerDuck/Resources/Languages/Translations.resx@@ -266,7 +266,7 @@<value>Caution</value></data><data name="Optimizer.UI.Risk.Risky" xml:space="preserve">- <value>Risky</value>+ <value>Expert</value></data><data name="OptimizationDetailsDialog.DetailedDescription" xml:space="preserve"><value>Detailed description</value>@@ -355,6 +355,9 @@<data name="Revert.Registry.Description.DeleteKey" xml:space="preserve"><value>Delete registry key: {0}</value></data>+ <data name="Revert.Registry.Description.RevertUnknown" xml:space="preserve">+ <value>Revert registry: {0}</value>+ </data><data name="Revert.Error.FileNotFound" xml:space="preserve"><value>Revert file not found</value></data>@@ -652,9 +655,7 @@<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.ShortDescription" xml:space="preserve"><value>Installs a custom performance-focused power plan to ensure your system always runs at maximum speed.</value></data>- <data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Downloading" xml:space="preserve">- <value>Downloading power plan...</value>- </data>+<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Importing" xml:space="preserve"><value>Importing and activating power plan...</value></data>diff --git a/optimizerDuck/Resources/Languages/Translations.vi-VN.resx b/optimizerDuck/Resources/Languages/Translations.vi-VN.resxindex 442029d..c585483 100644--- a/optimizerDuck/Resources/Languages/Translations.vi-VN.resx+++ b/optimizerDuck/Resources/Languages/Translations.vi-VN.resx@@ -260,7 +260,7 @@<value>Cẩn thận</value></data><data name="Optimizer.UI.Risk.Risky" xml:space="preserve">- <value>Nguy hiểm</value>+ <value>Chuyên gia</value></data><data name="OptimizationDetailsDialog.DetailedDescription" xml:space="preserve"><value>Mô tả chi tiết</value>@@ -352,6 +352,9 @@<data name="Revert.Registry.Description.DeleteKey" xml:space="preserve"><value>Xóa registry key: {0}</value></data>+ <data name="Revert.Registry.Description.RevertUnknown" xml:space="preserve">+ <value>Hoàn tác registry: {0}</value>+ </data><data name="Revert.Error.FileNotFound" xml:space="preserve"><value>Không tìm thấy tệp hoàn tác</value></data>@@ -634,9 +637,7 @@<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.ShortDescription" xml:space="preserve"><value>Kích hoạt sơ đồ năng lượng đặc biệt giúp máy luôn đạt hiệu năng cao nhất. (Có thể làm tăng nhiệt độ).</value></data>- <data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Downloading" xml:space="preserve">- <value>Đang tải power plan...</value>- </data>+<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Importing" xml:space="preserve"><value>Đang import và set active power plan...</value></data>diff --git a/optimizerDuck/Resources/Languages/Translations.zh-CN.resx b/optimizerDuck/Resources/Languages/Translations.zh-CN.resxindex 602ee6f..e3f35c8 100644--- a/optimizerDuck/Resources/Languages/Translations.zh-CN.resx+++ b/optimizerDuck/Resources/Languages/Translations.zh-CN.resx@@ -272,7 +272,7 @@<value>谨慎</value></data><data name="Optimizer.UI.Risk.Risky" xml:space="preserve">- <value>风险</value>+ <value>专家</value></data><data name="OptimizationDetailsDialog.DetailedDescription" xml:space="preserve"><value>详细说明</value>@@ -361,6 +361,9 @@<data name="Revert.Registry.Description.DeleteKey" xml:space="preserve"><value>删除注册表项:{0}</value></data>+ <data name="Revert.Registry.Description.RevertUnknown" xml:space="preserve">+ <value>还原注册表:{0}</value>+ </data><data name="Revert.Error.FileNotFound" xml:space="preserve"><value>未找到还原文件</value></data>@@ -652,9 +655,7 @@<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.ShortDescription" xml:space="preserve"><value>安装定制的高性能电源计划,让系统始终以最高速度运行。</value></data>- <data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Downloading" xml:space="preserve">- <value>正在下载电源计划...</value>- </data>+<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Importing" xml:space="preserve"><value>正在导入并激活电源计划...</value></data>diff --git a/optimizerDuck/Resources/Languages/Translations.zh-TW.resx b/optimizerDuck/Resources/Languages/Translations.zh-TW.resxindex a4286f8..728290c 100644--- a/optimizerDuck/Resources/Languages/Translations.zh-TW.resx+++ b/optimizerDuck/Resources/Languages/Translations.zh-TW.resx@@ -247,7 +247,7 @@<value>謹慎</value></data><data name="Optimizer.UI.Risk.Risky" xml:space="preserve">- <value>高風險</value>+ <value>專家</value></data><data name="OptimizationDetailsDialog.DetailedDescription" xml:space="preserve"><value>詳細說明</value>@@ -603,9 +603,7 @@<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.ShortDescription" xml:space="preserve"><value>安裝專為效能設計的自訂電源計畫,確保您的系統始終以最高速度執行。</value></data>- <data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Downloading" xml:space="preserve">- <value>正在下載電源計畫...</value>- </data>+<data name="Optimizer.PowerManagement.InstallOptimizerDuckPowerPlan.Progress.Importing" xml:space="preserve"><value>正在匯入並啟用電源計畫...</value></data>@@ -1303,6 +1301,9 @@<data name="Revert.Registry.Description.DeleteKey" xml:space="preserve"><value>刪除登錄檔機碼:{0}</value></data>+ <data name="Revert.Registry.Description.RevertUnknown" xml:space="preserve">+ <value>還原登錄檔:{0}</value>+ </data><data name="Optimizer.SecurityAndPrivacy.DisableErrorReporting.Name" xml:space="preserve"><value>停用錯誤報告</value></data>diff --git a/optimizerDuck/optimizerDuck.csproj b/optimizerDuck/optimizerDuck.csprojindex cab854d..e7c811a 100644--- a/optimizerDuck/optimizerDuck.csproj+++ b/optimizerDuck/optimizerDuck.csproj@@ -9,8 +9,8 @@<Authors>fatDuck</Authors><ApplicationIcon>Logo.ico</ApplicationIcon><Company>fatDuck</Company>- <FileVersion>2.13.3</FileVersion>- <Version>2.13.3</Version>+ <FileVersion>2.14.0</FileVersion>+ <Version>2.14.0</Version><Product>optimizerDuck</Product><Copyright>Copyright fatDuck 2026</Copyright><AssemblyTitle>optimizerDuck</AssemblyTitle>@@ -42,14 +42,14 @@<ItemGroup><PackageReference Include="CommunityToolkit.Mvvm" Version="8.4.2" />- <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.7" />- <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.7" />- <PackageReference Include="Microsoft.Extensions.Hosting.Abstractions" Version="10.0.7" />+ <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="10.0.8" />+ <PackageReference Include="Microsoft.Extensions.Hosting" Version="10.0.8" />+ <PackageReference Include="Microsoft.Extensions.Hosting.Abstractions" Version="10.0.8" /><PackageReference Include="Newtonsoft.Json" Version="13.0.4" /><PackageReference Include="Serilog" Version="4.3.1" /><PackageReference Include="Serilog.Extensions.Hosting" Version="10.0.0" /><PackageReference Include="Serilog.Sinks.File" Version="7.0.0" />- <PackageReference Include="System.Management.Automation" Version="7.6.1" />+ <PackageReference Include="System.Management.Automation" Version="7.6.2" /><PackageReference Include="TaskScheduler" Version="2.12.2" /><PackageReference Include="WPF-UI" Version="4.3.0" /><PackageReference Include="WPF-UI.DependencyInjection" Version="4.3.0" />@@ -64,6 +64,7 @@<ItemGroup><EmbeddedResource Include="Resources\Embedded\Icons\blank.ico" />+ <EmbeddedResource Include="Resources\Embedded\PowerPlans\optimizerDuck.pow" /></ItemGroup><ItemGroup>