[GH-ISSUE #709] NBFC.exe won't stay open #627

New issue

Closed

opened 2026-02-26 00:33:10 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 00:33:10 +03:00

Owner

Originally created by @MegaMongoose on GitHub (Jun 13, 2019).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/709

I cannot find the config for my Acer Aspire V5-591g so I wanted to try the recommend function. But nbfc.exe won't stay open. It flashes for a second and then closes.

I tried opening it as admin, still no luck. There is no error message, the shell just flashes and disappears.

2019-06-13 14:13:52.5246;Info;Starting NoteBookFanControlService;;NbfcService.NoteBookFanControlService.OnStart;ThreadPoolWorkQueue.Dispatch => QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem => ExecutionContext.Run => ExecutionContext.RunInternal => ServiceBase.ServiceQueuedMainCallback => NoteBookFanControlService.OnStart

Originally created by @MegaMongoose on GitHub (Jun 13, 2019). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/709 I cannot find the config for my Acer Aspire V5-591g so I wanted to try the recommend function. But nbfc.exe won't stay open. It flashes for a second and then closes. I tried opening it as admin, still no luck. There is no error message, the shell just flashes and disappears. 2019-06-13 14:13:52.5246;Info;Starting NoteBookFanControlService;;NbfcService.NoteBookFanControlService.OnStart;ThreadPoolWorkQueue.Dispatch => QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem => ExecutionContext.Run => ExecutionContext.RunInternal => ServiceBase.ServiceQueuedMainCallback => NoteBookFanControlService.OnStart

kerem

2026-02-26 00:33:10 +03:00

closed this issue
added the
Stale
label

kerem commented

2026-02-26 00:33:10 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 12, 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 12, 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