All of our HP ProBook 440 / 540 G8 laptops experiencing lagging / slow / stuttering as of April 2022

[FMUSA]

Yes, SP141624 should contain the workaround.

[DBAETEN]

Hi,

Any idea if a fix for the 650 series is also in the pipeline? we are facing the same issues on our 650 as on our 450's.

[FMUSA]

HI @DBAETEN, 

The same workaround applies to different models.  You can check if the same SP is posted under your system model.  If it's not posted, it should be soon.  Can you let me know the model year of your 650 and 450?  Are they also G8?

Thanks!

[DBAETEN]

the 650's are indeed G8 aswell, we noticed a surge in affected machines since recently , have been running HP Image assistant and turning of the fortimedia APO service to fix it for now.

[FMUSA]

The workaround in SP141624  should work for other G8 systems.  Please give that a try.  If you are able to extract the SP file, you can install just the Fortemedia related components or use it in your deployment package if you have one. 

[Pietro67]

I have about 50 HP Probook 650G8 (with 16.32 and 64 Gb Ram) with memory allocation at 100% for no admin user.

We have Microsoft Defender solution and I can see a lot of event in device in timeline (every second)  for :

8/22/2022, 10:48:27.427 AM
FMService64.exe created process regini.exe system services.exe > FMService64.exe > regini.exe ProcessCreated

8/22/2022, 10:48:27.423 AM
regini.exe created process conhost.exe a.xxxxxo FMService64.exe > regini.exe > conhost.exe ProcessCreated

8/22/2022, 10:48:26.395 AM
regini.exe created process conhost.exe a.xxxxxo FMService64.exe > regini.exe > conhost.exe ProcessCreated

8/22/2022, 10:48:26.392 AM
FMService64.exe created process regini.exe system services.exe > FMService64.exe > regini.exe ProcessCreated

The issue is not present with a local admin user.

I try now to disable Fortmedia service and check if something change.

Also i can't find fixed Realtek audio driver for 650G8 (only for 450 G8 ). Can you confirm that it is rhe same driver ?

Thanks

Update

restarting laptop with admin user temporary fix the porblem but a new windows update run with no admin user causes the problem to reoccur. This also with the last Realtek driver update from Microsoft Update.

[FMUSA]

Yes, the same underline workaround applies.  You can use the SP indicated or you can wait for HP to add a specific SP under the system model(s) that applies to you.

[acherm]

Saw this problem on multiple Probook 640 G8 and Probook 440 G8 laptops. It began to occur after a Windows update.

Symptoms: memory usage would slowly creep up 1% to 2% every few minutes. After around 90 minutes, the memory usage would be near max (95-99% used) and the system would become super slow, laptop fan would turn on.

Rather than roll back updates, we disabled a service named "Fortemedia APO", per suggestion from Jthuillie (https://h30434.www3.hp.com/t5/Business-Notebooks/HP-ProBook-450-G8-Notebook-PC-run-very-very-slowly/...) and the problem was solved.

[FrankOH]

Agreed ... disabling that service is still the resolution we go with.  Don't really have the time to check different versions of that or Realtek on multiple laptops. If any more of our employees have that issues (one did last week), we just disable the service, restart, and they're good.

It's a shame drivers aren't tested thoroughly enough that you have to keep dealing with fixes / rollbacks / etc.  I'm a PC person, but since I work on both PCs and Macs, one of the things I do like about the Macs is the lockdown hardware / software compatibility.  I very seldom have to worry about something like driver issues on Macs!

And speaking of driver rollbacks, in case anyone is having blue screen crashes on the HPs with an offending file at the bottom listed as: Netwtw10.sys ... we've discovered it's an issue with some Intel Wi-Fi cards and the driver.   The driver versions 22.140... or 22.150... casue a lot of blue screens (oddly enough, ONLY when in our office, not outside the office).  We had to rollback that particular Intel wi-fi driver to anything between 22.50... and 22.110...

[FMUSA]

I can assure you the drivers are well tested.  It may be hard to perceive that but I can assure you it is.  There are many layers of QA that goes into this process.  The issue appears to be related to an OS update that changed the behavior of certain API that was used.  The updated driver packs are being released and they should reach the systems shortly.