-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default screenshot location is C:\Windows\System32 #338
Comments
How did you solve this issue? |
@Ho-Ro My apologise, this was a user error, not caused by the software. OpenHantek (Windows version) apparently saves the screenshots into the folder it has been started from, i.e. not into a fixed location (as would be for example user's profile directory or the "Pictures" subfolder). Therefore when I start the OpenHantek by clicking the program icon in the folder where it's stored, screenshots work OK. But I was running it by using windows default search function: |
I just thought about this reason. I had no access to a win system during last week, so I couldn't check. Maybe a possibility could be to create a link where you can define the default location. Another option is to use the menu entry |
fix for OpenHantek/openhantek#338 Signed-off-by: Martin <Ho-Ro@users.noreply.github.com>
@misch2 You posted in the wrong project - this is the old and unmaintained predecessor. Nevertheless, I added a rough error message window to OpenHantek6022, that is shown when the export (screenshot & hardcopy as well as CSV & JSON) fails, e.g. due to missing rights or write protection), available in latest unstable |
I'm running OpenHantek6022 version 3.3.2.2 on Windows 11.
I downloaded and extracted it into a folder under my profile:
When I run it and try to produce a screenshot or a hardcopy, it tries to save the result into the Windows
system32
subfolder, as confirmed by process monitor:This action fails due to permissions, but OpenHantek doesn't indicate the screenshot failure in any way.
My suggestions are:
%APPDATA%\OpenHantek
, or into the standard windows "Pictures" folder in user profile.The text was updated successfully, but these errors were encountered: