[GH-ISSUE #303] From "enabled" to "read only" after restart #273

New issue

Closed

opened 2026-02-26 00:32:12 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 00:32:12 +03:00

Owner

Originally created by @soxfan82 on GitHub (Aug 2, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/303

Hi,

This is a fantastic program, thank you so much for creating it. You've turned a notebook I hated using into one I love using.

I have just one issue. Every time I restart my computer, it goes from "enabled" back to "read only" and I have to manually open the program to put it back. I have "start with Windows" and "close to tray" both checked.

Thanks!

Originally created by @soxfan82 on GitHub (Aug 2, 2017). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/303 Hi, This is a fantastic program, thank you so much for creating it. You've turned a notebook I hated using into one I love using. I have just one issue. Every time I restart my computer, it goes from "enabled" back to "read only" and I have to manually open the program to put it back. I have "start with Windows" and "close to tray" both checked. Thanks!

kerem

2026-02-26 00:32:12 +03:00

closed this issue
added the
Stale
label

kerem commented

2026-02-26 00:32:13 +03:00

Author

Owner

@hirschmann commented on GitHub (Aug 3, 2017):

Maybe your issue is caused by some known incompatibility.
If this isn't the case, please update to NBFC 1.5.3 beta, try to reproduce the error and then attatch the service log here.

@hirschmann commented on GitHub (Aug 3, 2017): Maybe your issue is caused by some [known incompatibility](https://github.com/hirschmann/nbfc/wiki/FAQ#are-there-any-known-incompatibilities-with-nbfc). If this isn't the case, please update to _NBFC 1.5.3 beta_, try to reproduce the error and then attatch the [service log](https://github.com/hirschmann/nbfc/wiki/Files-and-directories-overview) here.

kerem commented

2026-02-26 00:32:13 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 10, 2019):

This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed

@github-actions[bot] commented on GitHub (Dec 10, 2019): This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed