v1.1 Beta 4

v1.1 Beta 4

Important

Windows has recently begun flagging WinRing0 (the driver YAMDCC uses for EC access) as malware. See this discussion for more information.

This beta removes the Fan Overclocking feature introduced as part of the April Fools' update. That is all.

---

The YAMDCC updater currently has a known bug which may cause it to fail to install an update (accompanied by an error message).

See issue #62.

If you're having trouble updating YAMDCC, try the following steps:

1. Uninstall the YAMDCC service (without deleting YAMDCC data).
2. Reboot your computer.
3. Try updating YAMDCC again.
4. Open the config editor, and re-install the YAMDCC service.
5. If you had automatic update checks enabled, you will have to re-enable them from the Updater.

One last thing: in case of issues with new features, you might want to check your calendar.

v1.1 Beta 3

Important

Windows has recently begun flagging WinRing0 (the driver YAMDCC uses for EC access) as malware. See this discussion for more information.

This beta fixes various bugs, and introduces an all new Fan Overclocking feature!

Summary of changes since v1.1 Beta 2:

• Fix crash on update if the YAMDCC service is not installed
• Use temporary folder to download and install updates from (fixes issues with not having Admin privileges before installing the update)
  • Your old version of YAMDCC will no longer be kept after an update. You have been warned.
• Keep YAMDCC service install/uninstall logs for debugging
  • They are located in the YAMDCC install directory, and are called yamdccsvc.InstallLog and InstallUtil.InstallLog.
• Reliability improvements to YAMDCC service
• Added a new feature: Fan Overclocking
  • To enable, open the config editor, go to Options > Experimental features and click Enable fan overclocking.
  • While enabled, your maximum fan speed will double (for most YAMDCC configs, this will be 200%).
  • This feature is still experimental, and as such may not work every time (or at all).

Click here for the full changelog.

---

The YAMDCC updater currently has a known bug which may cause it to fail to install an update (accompanied by an error message).

See issue #62.

If you're having trouble updating YAMDCC, try the following steps:

1. Uninstall the YAMDCC service (without deleting YAMDCC data).
2. Reboot your computer.
3. Try updating YAMDCC again.
4. Open the config editor, and re-install the YAMDCC service.
5. If you had automatic update checks enabled, you will have to re-enable them from the Updater.

One last thing: in case of issues with new features, you might want to check your calendar.

v1.1 Beta 2

This beta fixes a few bugs (including a crash) related to hotkey registration with Windows, as well as a few UI fixes and some tooltips.

Summary of changes since v1.1 Beta 1:

• Fix crash on hotkey config apply and on exit when unregistering old hotkeys
• Fix hotkeys not functioning on first startup (before the Apply button is clicked)
• Add multi-instance detection of Hotkey Handler
  • Currently the already-running Hotkey Handler will not be restored due to a bug. This will be fixed in a future release.
• Check for admin privileges and installed/running YAMDCC service before starting Hotkey Handler
• Show scroll bars when a lot of hotkeys are added to the config window
• Add "Show hotkey configurator" option to tray icon (does the same thing as double-clicking the tray icon)
• Integrate YAMDCC's crash dialog into Hotkey handler
• Fix TAB indexing of hotkey UI
• Fix missing program title, author and copyright information from HotkeyHandler.exe
• Remove unused/debug code
• Small bug fixes and optimisations

Click here for the full changelog.

---

The YAMDCC updater currently has a known bug which may cause it to fail to install an update (accompanied by an UnauthorizedAccessException, or an error message starting in this version).

See issue #62.

If you're having trouble updating YAMDCC, try the following steps:

1. Uninstall the YAMDCC service (without deleting YAMDCC data).
2. Reboot your computer.
3. Try updating YAMDCC again.
4. Open the config editor, and re-install the YAMDCC service.
5. If you had automatic update checks enabled, you will have to re-enable them from the Updater.

v1.1 Beta 1

This beta introduces the long-awaited Hotkey Handler, along with some fixes from older versions.

It should be safe to update to this beta if you don't use the new Hotkey Handler app, but is still being released as a beta because the Hotkey Handler is still very new and untested.

Summary of changes since v1.0.3:

• Added a new application: Hotkey Handler
  • Hotkey Handler can be used to bind hotkeys to certain actions (but you could probably tell that from the title).
  • Hotkey Handler supports the following actions:
    • Open config editor
    • Toggle Full Blast
    • Toggle Win/Fn swap
    • Increase keyboard backlight
    • Decrease keyboard backlight
    • Change fan profile
    • Change default performance mode
  • Hotkey Handler's hotkeys will be active as long as the application is open and minimised, and the Enable hotkeys check box (under the Options menu) is ticked.
  • Note that the "Change fan profile", "Change default performance mode", and "Toggle Win/Fn swap" actions will be reverted next time the current YAMDCC config is applied.
• Add extra YAMDCC service commands (Not backward compatible with older YAMDCC versions, due to re-arranging some existing commands):
  • Change fan profile
  • Change default performance mode
  • Change Win/Fn swap (enabled, disabled, or toggle)
• The FullBlast command has been renamed to SetFullBlast, and now supports toggling Full Blast (if -1 is passed as a parameter).
• Fix the YAMDCC updater trying to access folders it shouldn't
  • For some reason Windows thought we were trying to access the System32 folder???
• Add an error message if the YAMDCC updater fails to delete the old YAMDCC installation due to files/folders being in use
  • This is related to issue #62. If you have more information on how
    to trigger this bug, please comment on the linked issue with reproduction steps so I can hopefully fix it.
• Re-wrote the EC Inspector to not rely on the YAMDCC service being running (or even installed)
  • Command syntax is slightly different now. Type "help" for help (without any hyphens)
• Fix DPI scaling for some UI elements in Config Editor
• Other small UI tweaks and optimisations
• Update dependencies:
  • TaskScheduler: v2.11.0 -> v2.12.1

Click here for the full changelog.

---

The YAMDCC updater currently has a known bug which may cause it to fail to install an update (accompanied by an UnauthorizedAccessException, or an error message starting in this version).

See issue #62.

If you're having trouble updating YAMDCC, try the following steps:

1. Uninstall the YAMDCC service (without deleting YAMDCC data).
2. Reboot your computer.
3. Try updating YAMDCC again.
4. Open the config editor, and re-install the YAMDCC service.
5. If you had automatic update checks enabled, you will have to re-enable them from the Updater.

v1.0.3

This release fixes a regression from v1.0.2 with fan profile add/delete, as well as an updater crash if the Configs folder was moved or deleted from YAMDCC's install directory.

Click here for the full changelog.

Hotkey Handler is up next if no more bugs get discovered in the meantime.

---

The YAMDCC updater currently has a known bug which may cause it to fail to install an update (accompanied by an UnauthorizedAccessException).

If you're having trouble updating YAMDCC, try the following steps:

1. Uninstall the YAMDCC service (without deleting YAMDCC data).
2. Reboot your computer.
3. Try updating YAMDCC again.
4. Open the config editor, and re-install the YAMDCC service.
5. If you had automatic update checks enabled, you will have to re-enable them from the Updater.

v1.0.2

This release contains bug fixes for the EC firmware version feature introduced in v1.0.1, as well as a new per-profile performance mode setting.

Summary of changes since v1.0.1:

• Add per-profile performance mode setting to fan profile config
  • The old performance mode setting now sets the default performance mode to be used when not overriden by the per-profile setting.
  • Configs made for v1.0.2 should be backwards-compatible with older YAMDCC versions.
• Fix service crash due to an EC firmware date parsing error
• Fix EC firmware version/date not being obtained if the YAMDCC service didn't have a valid config loaded on startup

Click here for the full changelog.

Hotkey Handler will eventually be completed, however I have also been working on another project for the past few days.

v1.0.1

This is a smaller release adding a couple more configs and EC firmware version logging.

Summary of changes since v1.0:

• New configs:
  • MSI Alpha 17 C7VF (#56)
  • MSI Bravo 15 B7ED (#60)
• Add EC firmware version to laptop info tab in config editor
  • If you are someone who's contributed a config to YAMDCC, please open a pull request to update your config to have an EC firmware version and date for your laptop.
• Fix some inconsistent fan profile descriptions for all configs
• Change the YAMDCC service "crashed on startup" message to "failed to start", and link to the FAQ for steps to fix it if the YAMDCC service was moved
• Update dependencies:
  • MessagePack: v3.1.2 -> v3.1.3

Click here for the full changelog.

(Note: Hotkey Handler is not ready for production, and is not included in this release as a result.)

v1.0

After nearly eight months and over 300 commits (plus the year before I released this project), YAMDCC is finally ready for a full release!

v1.0 comes with configs (and full support) for 5 laptops:

• MSI Crosshair 17 B12UGZ
• MSI GF63 Thin 11SC
• MSI Modern 15 A5M
• MSI Katana GF66 12UG
• MSI Titan GT77HX 13VH

Many more MSI laptops are likely to be supported with the generic configs.

Summary of changes since v1.0 RC:

• Fix update checks (again)
• Add decoded text display to EC Inspector
• Add success dialogs to service stop and uninstall
• Update dependencies:
  • MessagePack: v3.1.1 -> v3.1.2
• Minor bug fixes and optimisations

Click here for the full changelog.

v1.0 RC

This is it folks, hopefully the last update before the full 1.0 release!

A few more updater fixes this time around.

Summary of changes since v1.0 Beta 8 (hotfix 1):

• Add configs for the following laptops:
  • MSI Crosshair 17 B12UGZ (#48)
  • MSI Titan GT77HX 13VH (#49)
• Add success dialogs to service stop and uninstall
• Fix crash when attempting to check for updates from the YAMDCC config editor if the updater (Updater.exe) couldn't be found
• Fix updater not passing file path arguments with spaces correctly
• Better version detection
• Close/kill all running instances of YAMDCC (both the config editor and EC Inspector) before installing an update
  • The YAMDCC service is already stopped before updating
• Back up YAMDCC configs from previous versions before updating
  • They would get moved to the Old folder, then get permanently deleted if updating again

Click here for the full changelog.

No one reported any config editor bugs since the last release. Either that means I'm a better programmer than I expected, or the bugs haven't been found yet...

Please report any bugs you find to the issue tracker.

v1.0 Beta 8 (hotfix 1)

This is a hotfix release to fix a few updater bugs:

• Fix crash when no releases are found during a background update check
• Fix potential bug causing the updater to rank beta releases as "more up-to-date" than full releases
• Try to update to the latest pre-release if no regular release is found

Click here for the full changelog.

See v1.0 Beta 8 for changes between Beta 7 and 8.

More updater fixes are likely to come in the RC, mainly relating to determining whether the latest (pre-)release is more or less up-to-date than the current version.