Skip to content
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

Unable to save application settings on Windows 2016 Server #2412

Open
jwfx opened this issue Feb 3, 2025 · 5 comments
Open

Unable to save application settings on Windows 2016 Server #2412

jwfx opened this issue Feb 3, 2025 · 5 comments

Comments

@jwfx
Copy link

jwfx commented Feb 3, 2025

Brief description of your issue

On closing 3.2.25011 or whenever triggering something that causes a save of the settings, a popup like this appears and nothing is saved.

Image

  • User has admin rights and the settings xml can be modified and saved manually without any problem.
  • A known good version is 3.0.7660 so it might be a regression.
  • At the time of writing Canary has the same problem

Steps to reproduce (optional)

  1. Copy the portable (systeminformer-3.2.25011-release-bin) on a Windows 2016 Server machine
  2. Run the application
  3. Exit the application

Expected behavior (optional)

No response

Actual behavior (optional)

No response

Environment (optional)

OS Name:                   Microsoft Windows Server 2016 Standard
OS Version:                10.0.14393 N/A Build 14393
OS Configuration:          Standalone Server
@lilking420
Copy link

lilking420 commented Feb 3, 2025

I'm getting the same thing when exiting System Informer on Windows 10

@jwfx
Copy link
Author

jwfx commented Feb 3, 2025

I'm getting the same thing when exiting System Informer on Windows 10

Any chance that this is an older build? So far this only ever happened to me on Win Server 2016.

@eXense-auth
Copy link

I have the same problem
version 3.2.25011.2103 portable mode
windows 11 pro 26100.2894

@therube
Copy link

therube commented Feb 4, 2025

Might this be related, #2376 ?
And directory permissions are mentioned here, #2396 (comment).

@diversenok
Copy link
Contributor

If it says "The request is not supported", it means System Informer attempted to perform an operation (like an advanced file rename) that is either not implemented (for old versions of Windows) or not available on the specific filesystem. Permission issues would give "access denied" instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants