[GH-ISSUE #690] Doesn't function after Windows 10 v1903 Update (Here's Why and Solution) #611

Closed
opened 2026-02-26 00:33:07 +03:00 by kerem · 13 comments
Owner

Originally created by @ghost on GitHub (May 22, 2019).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/690

Hey hirschmann. I've upgraded my Windows to May 2019 update and NBFC has stopped functioning and shows an odd temperature number. Restarting the NBFC service or OS didn't work.

  • Windows 10, v1903, build 18362.116
  • NBFC 1.6.3

2019-05-22 171715

-Also tried reinstalling latest build again after deleting NBFC directories/settings and a reboot but didn't work.
-There is no hardware monitoring tools installed.

Originally created by @ghost on GitHub (May 22, 2019). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/690 Hey hirschmann. I've upgraded my Windows to May 2019 update and NBFC has stopped functioning and shows an odd temperature number. Restarting the NBFC service or OS didn't work. - Windows 10, v1903, build 18362.116 - NBFC 1.6.3 ![2019-05-22 171715](https://user-images.githubusercontent.com/50917967/58182288-0289fb00-7cb6-11e9-9a6e-707100da036a.jpg) -Also tried reinstalling latest build again after deleting NBFC directories/settings and a reboot but didn't work. -There is no hardware monitoring tools installed.
kerem 2026-02-26 00:33:07 +03:00
  • closed this issue
  • added the
    Stale
    info
    labels
Author
Owner

@XavierG96 commented on GitHub (May 24, 2019):

Same problem, updated to windows may 1903 and hasn't worked since. I have hp envy x360

<!-- gh-comment-id:495457186 --> @XavierG96 commented on GitHub (May 24, 2019): Same problem, updated to windows may 1903 and hasn't worked since. I have hp envy x360
Author
Owner

@ghost commented on GitHub (May 24, 2019):

A quite research and I've found out that the same problem occured with programs that utilizes "WinRing0 after the Windows 10 May Update". As ThrottleStop author unclewebb says "Starting with Windows 10 - 19H1, it looks like the Memory integrity setting can completely block the WinRing0 driver which will prevent ThrottleStop(NBFC in this case) from starting(utilizing WinRing0)."

So the solution is turning off the memory intergrity:

NOTE: Turning of Memory Integrity is a serious matter. Do not turn it off if you do not understand what you are doing. You may not be able to turn off Memory Integrity if your computer is joined to a corporate domain. Turning off memory integrity may violate your workplace's IT security policies.

The easiest way to disable memory integrity is via Windows Security as follows:

  1. Double click windows security in the tray or run it by searching for it by name.
  2. Select the Device Security Tab.
  3. Select "Core Isolation Details"
  4. Toggle off "Memory Integrity"
  5. Follow the prompts to restart your computer.
  6. Fresh install of NBFC if it needed.

And voilà, it works.

<!-- gh-comment-id:495471411 --> @ghost commented on GitHub (May 24, 2019): A quite research and I've found out that the same problem occured with programs that utilizes "WinRing0 after the Windows 10 May Update". As ThrottleStop author unclewebb says "**Starting with Windows 10 - 19H1, it looks like the Memory integrity setting can completely block the WinRing0 driver which will prevent ThrottleStop(NBFC in this case) from starting(utilizing WinRing0)**." So the solution is turning off the **memory intergrity**: _NOTE: Turning of Memory Integrity is a serious matter. Do not turn it off if you do not understand what you are doing. You may not be able to turn off Memory Integrity if your computer is joined to a corporate domain. Turning off memory integrity may violate your workplace's IT security policies._ The easiest way to disable memory integrity is via Windows Security as follows: 1. Double click windows security in the tray or run it by searching for it by name. 2. Select the Device Security Tab. 3. Select "Core Isolation Details" 4. Toggle off "Memory Integrity" 5. Follow the prompts to restart your computer. 6. Fresh install of NBFC if it needed. And voilà, it works.
Author
Owner

@XavierG96 commented on GitHub (May 24, 2019):

what are the risks of turning off memory integrity?

<!-- gh-comment-id:495497279 --> @XavierG96 commented on GitHub (May 24, 2019): what are the risks of turning off memory integrity?
Author
Owner

@XavierG96 commented on GitHub (May 24, 2019):

When i get in the Device Security tab it doesn't show "Core isolation details". It only shows "Security proccesor", "Secure boot", and "Standard Hardware security not supported"

<!-- gh-comment-id:495500097 --> @XavierG96 commented on GitHub (May 24, 2019): When i get in the Device Security tab it doesn't show "Core isolation details". It only shows "Security proccesor", "Secure boot", and "Standard Hardware security not supported"
Author
Owner

@ghost commented on GitHub (May 24, 2019):

"This feature is a subset of Core Isolation. Windows normally requires digital signatures for device drivers and other code that runs in low-level Windows kernel mode. This ensures they haven’t been tampered with by malware. When “Memory Integrity” is enabled, the “code integrity service” in Windows runs inside the hypervisor-protected container created by Core Isolation. This should make it nearly impossible for malware to tamper with the code integrity checks and gain access to the Windows kernel."

Maybe try using .reg file option and restart?
https://www.tenforums.com/tutorials/104025-turn-off-core-isolation-memory-integrity-windows-10-a.html

<!-- gh-comment-id:495569915 --> @ghost commented on GitHub (May 24, 2019): "This feature is a subset of Core Isolation. Windows normally requires digital signatures for device drivers and other code that runs in low-level Windows kernel mode. This ensures they haven’t been tampered with by malware. When “Memory Integrity” is enabled, the “code integrity service” in Windows runs inside the hypervisor-protected container created by Core Isolation. This should make it nearly impossible for malware to tamper with the code integrity checks and gain access to the Windows kernel." Maybe try using .reg file option and restart? https://www.tenforums.com/tutorials/104025-turn-off-core-isolation-memory-integrity-windows-10-a.html
Author
Owner

@XavierG96 commented on GitHub (May 25, 2019):

it is turned off, and still doesn't work. I guess I wont be able to use NBFC for a while.

<!-- gh-comment-id:495941166 --> @XavierG96 commented on GitHub (May 25, 2019): it is turned off, and still doesn't work. I guess I wont be able to use NBFC for a while.
Author
Owner

@XavierG96 commented on GitHub (May 26, 2019):

So I managed to get it working. I disabled virtualization technology in BIOS settings and tried the .reg option and it worked. Thanks a lot!

<!-- gh-comment-id:495967670 --> @XavierG96 commented on GitHub (May 26, 2019): So I managed to get it working. I disabled virtualization technology in BIOS settings and tried the .reg option and it worked. Thanks a lot!
Author
Owner

@Sidtech88 commented on GitHub (May 26, 2019):

For me disabling VT in BIOS setting did the trick

<!-- gh-comment-id:495969821 --> @Sidtech88 commented on GitHub (May 26, 2019): For me disabling VT in BIOS setting did the trick
Author
Owner

@musteb244 commented on GitHub (Jul 13, 2019):

After i updated Windows 10 v1903. NFC has been blocked. I uninstalled it and tried to install again but it can't be installed. I tried everything ( I disabled virtualization technology in BIOS settings, turned off memory integrity etc.) But it can't be installed by set up exe file. Help me please.

<!-- gh-comment-id:511156257 --> @musteb244 commented on GitHub (Jul 13, 2019): After i updated Windows 10 v1903. NFC has been blocked. I uninstalled it and tried to install again but it can't be installed. I tried everything ( I disabled virtualization technology in BIOS settings, turned off memory integrity etc.) But it can't be installed by set up exe file. Help me please.
Author
Owner

@github-actions[bot] commented on GitHub (Jan 11, 2020):

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

<!-- gh-comment-id:573251888 --> @github-actions[bot] commented on GitHub (Jan 11, 2020): 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
Author
Owner

@HeyImPuni commented on GitHub (Jul 16, 2020):

Even tho this issue is closed. It is, at least for me, not related to the Windows v1903 update. I'm on build 1809 and had an update yesterday, since then NBFC is only showing me negative temperatures and isn't controlling the fans. Core isolation is disabled (not even supported on my device).
Acer Aspire VN7-591G

BDa04uX7CM

EDIT:

I removed my latest Windows update (sorry, forgot to write it down). I'm on build 17763.1339.
It's probably this update

<!-- gh-comment-id:659365977 --> @HeyImPuni commented on GitHub (Jul 16, 2020): Even tho this issue is closed. It is, at least for me, not related to the Windows v1903 update. I'm on build 1809 and had an update yesterday, since then NBFC is only showing me negative temperatures and isn't controlling the fans. Core isolation is disabled (not even supported on my device). Acer Aspire VN7-591G ![BDa04uX7CM](https://user-images.githubusercontent.com/54338492/87668775-035cd680-c76d-11ea-82b2-a2bf38705534.png) EDIT: I removed my latest Windows update (sorry, forgot to write it down). I'm on build 17763.1339. It's probably [this update](https://support.microsoft.com/en-us/help/4566516/kb4566516-cumulative-update-for-net-framework)
Author
Owner

@joaofbravo commented on GitHub (Apr 14, 2023):

Also happened to me after an early 2023 Windows update (Asus TP301UJ)

<!-- gh-comment-id:1509081330 --> @joaofbravo commented on GitHub (Apr 14, 2023): Also happened to me after an early 2023 Windows update (Asus TP301UJ)
Author
Owner

@svetlisashkov commented on GitHub (Jul 27, 2023):

I have the same problem with Acer Aspire VN7-793G V17 Nitro BE and Windows 10 Pro 22H2 with the latest updates (July 2023).

<!-- gh-comment-id:1654663663 --> @svetlisashkov commented on GitHub (Jul 27, 2023): I have the same problem with Acer Aspire VN7-793G V17 Nitro BE and Windows 10 Pro 22H2 with the latest updates (July 2023).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nbfc-hirschmann#611
No description provided.