Welcome to Questions & Answers
Welcome to our community driven Questions & Answers (Q&A) forum. Please feel free to use this forum to ask and answer questions that pertain to our products.
NOTES:
• You can post questions and answers as a guest, or you can log in to post from an existing user account. If you do not have an account, then you can register to create a new one.
• A valid email address is required to post questions and answers. Your email address will not be published, nor will it be used for marketing purposes, etc. (as per our privacy statement).
• Logged in users can post questions and answers immediately (without needing to wait for them to be approved), comment on existing posts, bookmark posts as favorites, flag posts by other members (as spam, offensive, irrelevant, etc.), and view and edit their user profile.
• If you would like to display a custom avatar with your questions and answers, then you may create one for your email address using Gravatar.
• If you would rather ask us a private question, then you should use the Email Support page instead. However, please note that an existing license with a valid “Updates and Support” option is required in order to receive technical support via email.
- Mike asked 9 years ago
- last edited 4 years ago
- Posting this in here just in case anyone else has this issue. For WSEE Dashboard, I am getting a warning of “Computer monitoring error”. The details say “Cannot access the health of this computer because PowerShell is not available”. It is available and just in case I installed it again (using PS hehe): winget install –id Microsoft.PowerShell –source winget I have server 2025 standard with all the updates installed. However, I do use Explorer Patcher with my server 2025 machine. This error only started happening on a recent updated from EP. When I remove EP, the warning goes away. I know it’s not the responsibility of your software to play nice with all 3rd party software, but just wondering if you know of why this would happen and if it’s an easy fix on your end? If there isn’t a fix, it’s no biggie, I can just ignore the warning as the health monitoring still works. I love the functionality of WSEE and EP to disable either one LOL.
- starnge thing I just noticed. When I keep the Dashboard window up, the warning appears, then disappears, then reappears.
- In all my years of working with Essentials I’ve never come across such an issue before and so I don’t really have anything to offer you on this one I’m afraid. All I can tell you is that WSEE doesn’t belong to me… It’s a Microsoft product, and as such, I doubt that they’ll be willing to do anything for you (especially this late in the product’s lifecycle) if some other application, such as Explorer Patcher, etc., is conflicting with it. You’re probably 100% on your own there and will either need to remove EP from your server or you will need to contact them directly and see if they can assist you in resolving the problem over on their end. Essentials is heavily dependent on PowerShell and so if it’s not working properly then you will most likely run into lots of other issues as well (i.e., besides those health alerts).
- You must log in to post comments.
