Mind Pro - Crashes & Driver Failures (updated again 10/08/2026)

Mind Mind Pro
1

I have two of the Mind Pro flagship compute products from Khadas and have serious issues with the reliability or even the useability of these products. The initial behavior of the product is both disappointing and untrustworthy. While this is one of the most cutting edge products technologically in providing the Panther Lake 16th Gen CPU + Arc GPU + NPU and quiet cooling it is also among the most costly consumer computer products in the marketplace. Oddly, for such a high cost product, it ships with Windows Home rather than Pro and one would expect that the customer audience for a high tech high cost product would likely upgrade it to Win Pro and would do so with a clean install of Windows…I did…and have found that the drivers and/or hardware itself have serious issues:

  • the Power Mode settings in the Khadas “Mind” app are not respected by the hardware/OS interaction
  • unplugging the power supply is a feature of this product yet it frequently crashes the system immediately when the power adapter is unplugged
  • unplugging the power supply after a Windows Shut down results in a crash and system red-light condition when Power Mode is set to Hibernate or Sleep (not tested for Power Mode set to Battery)
  • unplugging the power supply after a Windows Hibernate results in a crash and system red-light condition when the Power Mode is set to Hibernate or Sleep (not tested for Power Mode set to Battery)
  • unplugging the power supply after a Windows Sleep results in the system immediately waking up from Sleep
  • the system does not respond to OS wake events, for example to run backup software on a schedule
  • the system does not follow the Power Mode setting to transition to Hibernate when unplugged (as noted above, it crashes)
  • there appear to be fundamental power interactions with the OS that the Khadas drivers do not handle as advertised or even do not handle correctly at all

This is what I did for upgrading/installing Win Pro:

  • resize and add/create a drive partition for data using Disk Management within the OS (fully supported approach by MS)
  • create an system image of the OEM installation as a fallback and saved to the data partition for test purposes
  • download and save the latest Win Pro ISO available from MS to the data drive
  • mount the ISO and start Windows setup.exe to start the Windows install process (have done this many times on many systems)
  • select saving nothing on the existing OS partition to create a scratch/clean OS install
  • use Shift-F10 at the connect to internet screen and run “oobe\bypassnro” to create a local account
  • complete the install and local account creation…successfully (yes, bypassnro still works from a mounted ISO install)
  • perform all Windows updates FIRST then install the most recent Khadas driver package: mind-pro-driver-v1.1-260818
  • perform Windows updates again AFTER the Khadas drivers package install

Things worth noting (the two Khadas units are noted as K1 and K2):

  • Winver after Win Pro install and updates on K1 showed 26200.9445 as the version
  • drive C actually showed the “Khadas” folder after Win Pro install and BEFORE the Khadas drivers package was installed !!!
  • the Khadas driver package install paused, as expected, at locations where large footprint drivers were being installed
  • Winver after the Win Pro install and updates on K2 (2 days later) showed 26200.9457 as the version
  • drive C again showed the “Khadas” folder BEFORE the Khadas drivers package was installed !!!
  • the Khadas driver package install did NOT pause at all and completed within 2 seconds and the command prompt screen appeared to show “Currently installed” for ALL Khadas drivers and components (note this is only 2 days after the K1) install)
  • running Windows update on K1 after seeing the 9457 version on K2 resulted in K1 being updated to 9457

Performance issues:

  • after the installs, including the Khadas drivers, testing reveals that the drivers are not or do not appear to be functioning or correctly if at all
  • the Khadas “Mind” app “Power Mode” settings do not appear to result in any differences in the system behavior when the power adapter is unplugged and, as noted above, crashes occur following various Windows shut down, hibernate, and sleep events
  • I have submitted support requests via chat and email in the last 2 days and have yet to receive any responses from Khadas (this is not a criticism…merely a note that Khadas has been informed of the issues)
  • clearly, if Windows is “Shut down” and thus, powered down, then in no way in any universe should unplugging the power adapter result in ANY effect on the system…much less a system red-light crash

Bottom Line:

  • the Mind Pro as it stands today is essentially unreliable as a consumer product
  • in particular for this reason: if the unit EVER loses power, the probable result is an immediate red-light crash of the Mind Pro
  • recovering from the crash is “possible” as i have done that several times now…but, there is NO consumer documentation for doing this and the average consumer will likely not be able to recover from a crash event without substantial, at cost, technical support
  • the product marketing literature is “spiffy” but, IMHO, the product is not ready for “Prime Time”…then again, maybe I am missing something obvious…???

If anybody can offer anything on the drivers issue or the issues with the interaction of the Mind Pro with Windows OS shut down, hibernate, sleep, or scheduled wake event…please do as i would like to have these fixed regardless of the source of the problems…be it me or Khadas or the “Easter Bunny”.

Follow-up (09/21/2026):

Additional testing has revealed information that may be useful for Khadas R&D to diagnose the issues:

  • The 30 second power button press has been what I have been using to successfully reboot the system. But, that is not the issue. The issue is that something is causing a crash or not allowing proper power transitions and rendering the system unreliable for everyday use. In fact, after additional testing there appear to be two separate issues:

  • #1: the issue of what is causing the crashes and power transition failures (see further info below)

  • #2: system wake timers are not waking the Mind Pro or the Mind Pro is responding to wake events in some manner that the OS does not detect at all

  • the system configuration is: Mind Pro + Asus VA34VCPSR monitor + Logitech K950 keyboard + Logitech M650 mouse

  • the keyboard and mouse are connected via Bluetooth

  • the monitor input connection is via USB-C which is required for use of the monitor hub (1 RJ-45 + 3 USB-A ports)

  • additional testing with various setting configurations has identified that the ASUS monitor is supplying power back to the Mind Pro thru USB-C Power Delivery and is conflicting with the Mind Pro power adapter power delivery. This may be due to the Mind Pro drivers or firmware not being able to parse the power delivery. In particular, when the Mind Pro power adapter is disconnected the OS battery icon in the system tray briefly displays the power disconnect and then immediately shows the power as connected again even though the power adapter is disconnected (unplugged). Thus, indicating power is being delivered or that the Mind Pro is indicating to the OS that it is powered. The behavior of the Mind Pro is affected by this power delivery issue.

After removing the USB-C connection and reverting to HDMI only:

  • battery operation became normal
  • battery charging became normal
  • OS Shutdown > unplug power > no system crash
  • resume from long sleep sessions became normal
  • OS Hibernate has not been tested
  • Mind Pro Power Mode has been set as “Use battery” for all testing to attempt to avoid crashes
  • Note: reverting to HDMI disables use of the monitor port hub and is not the intended in-service configuration

The wake event issue does not function regardless of using HDMI or USB-C for the monitor connection

  • powercfg /waketimers confirms the wake timer is present, but the system never wakes
  • the Event Viewer records no wake event at all at the scheduled time
2

Hello @galileo

We sincerely apologize for the unpleasant experience you’ve had. Our customer service team will follow up on your issue further.

3

I have communicated with Khadas Support (thru Vivian Wu) as well on this issue.

  • Issue #1: As of 9/22/2026 I can report that for the HDMI connection to the monitor all the Khadas Mind Pro Power Mode settings appear to work correctly with the OS for Sleep and Hibernate for plugged and unplugged power adapter cases…and, that using the USB-C monitor connection, due to its power backfeed thru the USB-C connection does result various misbehaviors of the Mind Pro including red-light crashes for some cases. This unfortunately may mean that monitors with port hubs cannot be used with the Mind Pro depending on power backfeed through the USB-C connection being provided.

  • Issue #2: the wake up to run scheduled tasks issue remains a problem as of 9/22/2026 and while further testing is ongoing, there is a possible pattern emerging: the Mind Pro wakes from Hibernate and allows scheduled tasks to run but, waking from Sleep is somewhat more nuanced in whether tasks run or not. This appears, subject to further testing, to relate specifically to network connectivity at the moment a task runs and requires a network connection i.e. something involving network access such as an NAS device. In particular, for a wireless connection: is the wireless stack running and connected at the moment task action calls for network access? This is where the failure pattern begins to emerge as waking from Hibernate is perhaps allowing enough time for the wireless connection to establish itself whereas waking from Sleep is faster and thus, affords less time for the wireless connection to be established before the task fails due to not finding the network path because the network is not found at all…this is where some further explorative testing is required.

At any rate, the OS wake and the Khadas hardware wake do function from Hibernation for tasks requiring a wireless network path whereas for wake from Sleep has an issue and the task fails to complete. And, that issue may well be related to the “S0” sleep state which the Mind Pro uses and which is noted in various commentaries to have issues specifically related to wake events and which are frequently related to how the firmware and/or driver design work with the “S0” Modern Standby sleep state.

Hopefully, Khadas R&RD will pick up on this issue and dig into this more deeply as they have access to their firmware and driver code as well as how the wireless network stack spins-up. This should be an issue that can be fixed as other manufacturers have managed to find solutions for “S0” + Wake from Sleep.

4

update 09/23/2026:

Additional testing indicates that the issue may not be related to network availability after wake. A Task Scheduler task configured to wake the system at 07:45 AM and write a file to a network-mapped drive did not execute at the scheduled time of 07:45 AM. The task actually executed at approximately 08:22 AM when the system was manually awakened. The OS Task Scheduler recorded the actual run time as the manual wake time rather than the scheduled wake time. This behavior mirrors the Bvckup application scheduled run failure pattern and suggests that scheduled activity is being deferred until after a manual wake occurs after a prolonged S0 Modern Standby period. Whereas, short duration sleep > wake tasks appear to work correctly. This appears more consistent with a wake-handling issue than with a post-wake network initialization issue.

I would appreciate Khadas responding to this issue as it has a significant negative impact on the system being able to handle scheduled tasks. As noted previously, the issue may well be related to how waking from the “S0” sleep state is being handled by the firmware and/or drivers.

I note again, that those same tasks are handled correctly by the Mind Pro when the system was sent to Hibernate rather than Sleep.

5

That is an incredible piece of troubleshooting, especially catching the USB-C Power Delivery conflict from the ASUS monitor! Power-delivery feedback loops over Type-C ports frequently confuse proprietary hardware switchers like the Mind Link/Mind Pro, leading to those exact phantom charging states, wake-timer failures, and red-light crash loops.

Isolating it to a power-negotiation glitch between the monitor’s built-in hub and Khadas’s power management firmware gives their R&D team an exact target for a future BIOS/driver patch. Thanks for documenting this deep dive it’ll definitely save other users a massive headache!

6

@ uredla: thx for your reply!

Update 09/24/2026:

Additional testing was completed using the same overnight Sleep scenario that previously failed to wake for scheduled tasks.

To determine whether aggressive power-management settings were contributing to the issue, the following settings were changed from their factory defaults:

  • PCI Express → Link State Power Management = Off (battery and plugged in)
  • Hard Disk → Turn Off Hard Disk After = Never
  • Sleep → Allow Wake Timers = Enabled (battery)

The system was then placed into Sleep overnight and allowed to remain unattended until after the scheduled 8:00 AM Bvckup wake event. The result was no change in the failed wake behavior.

  • The system did not wake at the scheduled time.
  • The Bvckup application scheduled backup job did not run.
  • No corresponding wake, resume, wake failure, or scheduled-task activity was recorded in Event Viewer around the scheduled wake time.

The system was manually awakened at approximately 8:52 AM. After manual wake:

  • Bvckup reported its normal 5-minute post-power-up delay.
  • The backup then ran successfully.
  • No errors were reported by Bvckup.
  • No indication of a failed or missed wake attempt was found in Event Viewer.

I have now reverted the modified power-management settings back to the original Khadas defaults so that any future testing remains consistent with the intended platform configuration.

At this point:

  • Wake from Hibernate continues to function correctly.
  • Wake from prolonged Sleep (S0 Modern Standby) continues to fail.
  • The issue is reproducible.
  • Windows power-plan adjustments do not appear to materially affect the behavior.

The evidence continues to suggest that the problem lies in the handling of prolonged S0 Modern Standby residency rather than in Windows wake-timer configuration, Task Scheduler configuration, or the backup application itself.

In addition, the System Event Log contains a continuous stream of WHEA-Logger Event ID 17 warnings at approximately 2 second intervals (so, yeah…there are a LARGE number of these !!!) throughout the overnight Sleep period. Of particular interest is that these WHEA Event ID 17 warnings continue throughout the period during which the scheduled wake event should have occurred. At the same time, no corresponding wake, resume, wake-failure, or task-execution events are recorded around the scheduled wake time.

I cannot determine whether these WHEA Event ID 17 warnings are directly related to the wake problem. However, because they occur continuously during the overnight S0 sleep interval and because the scheduled wake failure remains reproducible, I believe they warrant review by Khadas engineering.

The Event Viewer Event ID also shows that after the initial Sleep transition, additional power-related events continue to occur while the system is supposedly asleep. This suggests that the platform may still be undergoing internal power-state transitions after entering S0 Modern Standby.

Confirmed:

  • Hibernate wake functions correctly
  • Sleep wake continues to fail
  • Windows power-plan changes had no effect
  • Event ID 17 warnings continue throughout the overnight sleep interval

Conclusion:

  • The evidence continues to point toward a firmware, driver, ACPI, PCIe, or Modern Standby implementation issue rather than a Windows configuration issue.
  • A fundamental Windows OS capability is broken on the Mind Pro due to the issues that have been noted and confirmed.
  • This broken capability cannot be resolved by the user and cannot be resolved without deeper R&D team corrective action.

Could Khadas engineering please review this information and advise whether there are any known issues, diagnostic procedures, firmware updates, BIOS settings, or driver updates related to scheduled wake events from S0 Modern Standby?

Some reply from Khadas would be very appreciated so that “all us users” have some indication that the issue is being evalutated by Khadas…Thanks!

7

Update 9/26/2026:

Further testing has revealed that:

  • during system “Sleep” there is a flood of Event ID 17 Warnings that are specifically generated by the WHEA-Logger
  • these events are reported as “A corrected hardware error has occurred” for the “PCI Express Root Port”…without delving deep into the weeds, this is not related to user or OS actions, it is a Khadas hardware or firmware or driver issue that can only be corrected if Khadas will resolve it
  • this issue does not occur during system Hibernate as the resume/wake paths are likely somewhat different
  • any user of the Mind Pro (and perhaps any of the Mind series) “will” have this flood of Event Id 17 Warnings as these appear to be generated by repeated system action/events during the sleep cycle…the flood has one very interesting aspect to it: the events occur on a very consistent 2 minute (+/- a few seconds tolerance) interval throughout the entire duration of the sleep cycle (I previously noted this and mistyped the interval a 2 seconds rather than 2 minutes)
  • the consistency of the 2 minute intervals is a bit of a “smoking gun” as to part of the cause
  • there is an unexposed Windows UI setting for system unattended timeouts (that can be exposed to the UI via a registry switch) which, coincidently, is set by default to 2 minutes
  • the system unattended timeout is used by the OS for system wake events which occur with no user interaction…the purpose is to return the system to sleep if no system activity occurs within the timeout so that the system does not wake and never go back to a suspended state
  • changing the unattended timeout from its 2 minute default to some longer value (I used 10 minutes) results in the flood of Event ID 17 events stopping completely or being reduced to a single event over the entire sleep cycle
  • the events are occurring due to some deeper issue with what the Khadas hardware/firmware/drivers are doing during the sleep cycle that affects the PCI Express Root Port as noted above
  • there is no user action or OS tweaking that I know of that can resolve this problem
  • while I cannot “absolutely” confirm that this is the cause of the failure of the Mind Pro to wake for application wake calls or application scheduled tasks, it demonstrates a deeper issue with the Khadas system
  • I note that with all other systems that I own, there are no such issues and there are no fail to wake for “any” scheduled tasks regardless of OS generated tasks or application tasks…thus, the evidence points more towards a Khadas issue than anything else given the testing I have done

Thus, for the purpose of concluding this entire post topic, i note that the 2 original issues remain unresolved and remain entirely in Khadas’ court:

  • Issue #1: system crashes and/or instability due to power back feed from hubs that output power across USB-C connections…and, it is worth noting that the Mind Pro does NOT use a dedicated power input port which means that the USB-C ports MUST accept ANY incoming power, regardless of its source, for the system to work at all…further comment on this is speculation on any correlation with the problem
  • Issue #2: system wake failures for application generated wake calls are confirmed NOT to be recognized by the Mind Pro hardware/firmware/drivers while OS wake calls appear to work at least to the extent that they have occurred during the sleep cycles in my testing…and, the occurrence of the flood of Event ID 17 Warnings indicates that something that Khadas is doing “under-the-covers” during system Sleep is not functioning correctly as far as the OS is concerned

For those users of the Mind Pro who are interested, the system unattended timeout setting can be exposed in the UI via:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238c9fa8-0aad-41ed-83f4-97be242c8f20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0
  • changing the “Atrributes” values from “1” to “2” allows the UI to show the settings
  • the settings are shown in: Control Panel > Power Options > Change plan settings > Change advanced power settings > Sleep > System unattended sleep timeout…the OS default is 2 minutes and larger values allow the system to “wait” for an unattended activity to occur or run before the system returns to sleep

Finally, I want to note that Khadas has been silent as far as responses to these issues and to the entire amount of testing and troubleshooting information that has been presented to them here and through replies to their direct Support email address. And, as a user/customer of their “flagship” compute product, I am far beyond disappointed. Their “Support” could simply have noted that the issues have reproduced, or not, and are under evaluation…but, silence is equally simply a disrespectful “reply” to a customer.

…I’m done now…

8

Update 10/10/2026:

I have developed a workaround for the task wake failure issue that appears to work reliably. If there is any interest, I will post the workaround here…let me know…

9

Note: this post starts with a partial and edited re-post of my comments in: mayne921’s thread “Mind Pro constantly gets locked to 400MHz and battery gets corrupted”…this is for a brief background on what, IMHO, I have found on “my” two Mind Pro systems.

I have managed to achieve a stable Mind Pro configuration after many hours of configuration changes and testing…but, I am still wondering when yet another new “gotcha” will crop up. The power management firmware and drivers do have issues that have not been resolved. There are some workarounds that “appear” to stabilize the system or, at least, my system configuration.

These generally involve circumventing or neutering various items to prevent or minimize the power management transitions that occur during or as a result of the “S0” Modern Standby “Sleep” states. The longer an “S0” system is in “Sleep” the more power saving transitions there are occurring and the system goes deeper into “Sleep”. Those transitions are apparently involved in many, if not all, of the power issues…at least that is what I am seeing. The shorter time the system is in “Sleep” the fewer the number of power transitions that occur…thus, getting out “Sleep” and into “Hibernate” within some short period of time and the power transitions stop and the power issues disappear.

Transitioning from “Sleep” > "Hibernate requires using the “Hibernate after” capability of the system. The OS on the Mind Pro does not display “Hibernate after” in “Settings > System > Power & battery > Screen, sleep & hibernate timeouts”. This may be related to the Mind Pro being identified as an “S0” capable system or due to an OEM system capability that is presented or not presented in their configuration strings for the system. The configuration strings are defined by the OEM for their hardware not by users or by the OS.

While the “Hibernate after” settings are not available in “Settings” they can still be displayed in “Control Panel” via a registry setting. The “Hibernate after” function/behavior is still fully supported and fully operational within the OS and is still functional on the Mind Pro. Thus, a path to circumventing the power state transitions that start to occur due to Modern Standby deep sleep is still available. This is how my two Mind Pro systems are configured and have achieved a stable and reliable “Sleep after 15 minutes > Sleeping > Hibernate after 3 minutes > Hibernated” transition and along with a few other power related tweaks are avoiding the crashes and wake from sleep failures.

Also worth noting in particular is that my Mind Pro does not wake correctly for scheduled tasks which use the “Wake the computer to run this task” when the Mind Pro wakes from “Sleep” whereas the task will run correctly when it wakes from “Hibernate”. The task attempts to wake the computer from “Sleep” but, the task “Action” does not actually execute and the Mind Pro may or may not return to “Sleep” or may somtetimes crash (red-light crash).

The critical item here is that the Mind Pro DOES wake and run a task correctly when it wakes from “Hibernate” but, NOT from “Sleep”. Thus, for a repeating task (such as a daily overnight file backup to a server or NAS) the system MUST wake from “Hibernate”, run its task and, critically: return to “Hibernate” for the next task cycle to run.

Following are the settings I used to achieve a stable “Sleep” to “Hibernation” transition:

0: add/show “Hibernate” in the “Start > Power” menu:

  • [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FlyoutMenuSettings]
  • “ShowHibernateOption”=dword:00000001

1: add/show “Hibernate after” in "Control Panel > Power Options > Change plan settings > Change advanced power settings Advanced settings > Sleep:

  • [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238c9fa8-0aad-41ed-83f4-97be242c8f20\9d7815a6-7ee4-497e-8888-515a05f02364]
  • “Attributes”=dword:00000002

2: set Screen and Sleep timeouts for the “Plugged in” condition (battery can be changed but, the focus here is “Plugged in”)

  • “Start > System > Power & battery > Screen, sleep & hibernate timeouts > Plugged in” > …
  • “Turn my screen off after > 15 minutes” (change to your value after system is stable)
  • “Make my device sleep after > 15 minutes” (change to your value after system is stable)
  • note: “Hibernate after” is NOT shown here…it will be shown and set in Control Panel

3: set computer button action:

  • “Start > System > Power & battery > Power & sleep button controls > Plugged in” > …
  • “Pressing the power button will make my PC > Sleep” (or “Hibernate”…your choice)
  • “Pressing the sleep button will make my PC > Sleep” (or “Hibernate”…your choice)
  • set the “On battery” conditions to your preference for your battery use scenario

4: set “Hibernate After” timeout in Control Panel:

  • “Control Panel > Power Options > Change plan settings > Change advanced power settings Advanced settings > Sleep” > …
  • “Hibernate after > On battery > 3 minutes” (use short timeout to minimize “Modern Standby” deep sleep time !!!)
  • “Hibernate after > Plugged in > 3 minutes” (use short timeout to minimize “Modern Standby” deep sleep time !!!)
  • this setting results in transitioning the system from “Sleep” to “Hibernate” after the 3 minute timeout
  • this is the missing setting in “Settings > System > Power & battery > Screen, sleep & hibernate timeouts” !!!

5: set “Hard disk” timeout:

  • “Control Panel > Power Options > Change plan settings > Change advanced power settings Advanced settings > Hard disk” > …
  • Turn off hard disk after > On battery > 0 minutes (Never)"
  • Turn off hard disk after > Plugged in > 0 minutes (Never)"
  • this helps avoid various system and/or Event log Warning or Errors !!!)
  • the power usage for NVMe drives is trivial and not worth the potential for system “Errors”

6: set “PCI Express” state:

  • “Control Panel > Power Options > Change plan settings > Change advanced power settings Advanced settings > PCI Express” > …
  • “Link State Power Management > On battery > OFF”
  • “Link State Power Management > Plugged in > OFF”
  • this helps avoid various system “Errors” from faulty firmware or drivers !!!

7: set network Wi-Fi adapter power:

  • “Device Manager > Network adapters > Intel(R) Wi-Fi… > Power Management” > …
  • uncheck > “Allow the computer to turn off this device to save power”

8: set network ethernet adapter power (if you have an ethernet dongle or dock):

  • “Device Manager > Network adapters > ethernet adapter… > Power Management” > …
  • uncheck > “Allow the computer to turn off this device to save power”

9: settings in Khadas Mind App:

  • “Device Mode When Unplugged > Hibernate”
  • “Smart Charging > OFF” (this “appears” critical to the power transitioning behavior !!!)
  • note that you WILL NEED to turn this off again every 5 days as the Khadas firmware/drivers turn it on automatically after 5 days
  • this manual turn off again on a 5 day cycle will be necessary until the firmware/driver issues are resolved by Khadas
  • the issues with the Mind Pro crashing, overheating, failing to wake at all, or reverting to slow CPU speed “appear” to be firmware and driver related and the “Smart Charging” setting for some reason “appears”, per my experience to date, to avoid or at least be involved in these issues

---------- !!! ----------
At this point, the system will enter “Sleep” on its own via the sleep timeout or manually via the power button, or via “Start > Power > Sleep”. Then, 3 minutes after entering “Sleep” the system will transition from “Sleep” to “Hibernate”. Or, the system can be sent directly to “Hibernate” via “Start > Power > Hibernate” or, more “brutally” via unplugging the power if the Khadas “Device Mode When Unplugged” is set to “Hibernate”. From my experience, “Hibernate” is arguably a much more safe and reliable long duration (e.g. overnight) state for the system to be in.
---------- !!! ----------

After changing these settings on my two Mind Pro systems I am seeing “essentially” clean Event logs with only an occasional “Warning” or an “Error” for a “DCOM” event for a timing race condition or, as I understand it, for new items that MS has downloaded in the background that are not yet useable on the system but, which are trying to load as part of MS preparation/testing for future features or updates. My understanding is that these are generally harmless “Errors” but, show up in the Event log regardless of that and are disconcerting nonetheless.

I assume that if you read this far…LOL…then you are capable and comfortable with dealing safely with the registry. But, as always, if you make these changes to your system be sure to make a backup (export) of at least the relevant registry sections as a fallback or for reverting to the original registry sections if you want to revert/restore to your original state.

Last and optional item: if a task wake event will start a “delayed” action on system wake up, then you may need to adjust the “System Unattended Sleep Timeout”. This timeout is used to return a system to its suspended state (typically “Sleep”) for unattended (i.e. non-user initiated…say a midnight file backup) wake events when no action or activity occurs within the timeout period. The OS default is 2 minutes but, if you have some application that delays its execution for longer than the unattended timeout then the system will return to the suspended state without ever running that application’s task. The UI for the unattended timeout is not exposed/displayed by the OS by default but, following is how to show that UI so that you can adjust the timeouts:

0: add/show in “Control Panel > Power Options > Change plan settings > Change advanced power settings Advanced settings > Sleep” > …

  • [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\238c9fa8-0aad-41ed-83f4-97be242c8f20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0]
  • “Attributes”=dword:00000002
  • this adds “System unattended sleep timeout” and allows setting the timeouts
  • if you need this for delayed task execution then change the timeouts to be larger than the delayed action time
  • the actual values are located in: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\User\PowerSchemes\381b4222-f694-41f0-9685-ff5bb260df2e\238c9fa8-0aad-41ed-83f4-97be242c8f20\7bc4a2f9-d8fc-4469-b07b-33eb785aaca0]

Again, backup the relevant registry sections before enabling or changing anything

Finally, I wanted to post what I have found out from my testing (experimentation) as there appears to be some firmware/driver issue with proper powering/behavior of the system and/or its ports that results in various system and/or attached hardware errors. Generally, it seems that the aggressiveness of the power management is emerging as an issue for the Mind Pro. And, that aggressiveness is manifesting itself in a number of odd behaviors. At least, IMHO, this is what my experience with the Mind Pro seems to indicate to me, YMMV.

..post back with your results if you test this approach…