@CCTVCam you still have an extra space on the 3rd step between the / and startcomponentcleanup
I have ran @CCTVCam command recommendation. It ran without issue, and found no errors. It did not bring Windows up to the current version, it's still at 1909. Windows Update still shows many updates awaiting.
I installed the same .8681 video driver @VorlonFrog is running.
Now we wait and see.
Yes, updates were paused.My own pc is on 1909. Do you / him have update pause set? I'm guessing that's what it could be. Mine are paused.
Yes, updates were paused.
I unpaused, and of course updates immediately started happening. Computer has now been offline for 3+ hrs.
Will have to wait until someone gets home there to see what's up.
I'm going to hazard a guess that if you ran it without updates paused you'd probably get a later version. Question is do you want untested updates by running it unpaused? I'm guessing not if you have them paused.
If PC is still offline, doesn't sound like a Win issue. You could try running dism again. I've had occassions where something on the pc corrupted Win again without hours and I had to run it 3 times to get a version that stayed clean. I blame Win here as the 3rd time it stayed as it wa supposed to. Can't remmber if I blocked an update to achieve it. In this instance it sounds more like a BI Issue. Memory leaks are usually software. Have you tried an earlier known good version of BI or tried contacting their support guy to see if they can reproduce it?
It's been about 12 hours and memory usage is staying steady.I'm still experiencing this while testing the last 5 releases. I've reverted back to 5.3.6.7, which is the last stable release, and see if the leak stops.
I’m with you @looney2ns, this is beyond frustrating and it doesn’t seem specific to one particular Intel display driver.Well, after all the updating of Win10PRO to latest ver, and drivers, and updating BI to 5.3.6.7, nothing has changed. Still have memory creep at the same rate as I did at the start of this journey.
How much is it worth to you all to see an HP Elitedesk G2, thrown into the street, then repeatedly ran over by for 4X4 truck.
I've tried around 15 different Intel Drivers, all with the same exact result.I’m with you @looney2ns, this is beyond frustrating and it doesn’t seem specific to one particular Intel display driver.
I made Ken aware when I first started noticing it a few weeks ago. He didn't seem to think it was a BI issue.I've tried around 15 different Intel Drivers, all with the same exact result.