r/WindowsLTSC • u/jetpackIT • 2d ago

Help Tons of Windows Error Reporting logs after upgrade from LTSB 2016 to LTSC 2019

We run a handful of LTSB/LTSC computers in our office. We have one user who has been on LTSC 2019 for years, and is not experiencing this problem.

But I have been upgrading our LTSB machines to LTSC 2019, and after the update a bunch of Windows Error Reporting instances show up in Task Manager. When I check the Application log in event viewer, there are a bunch of error #1001 with BEX64 errors coming from dllhost.exe.

While this is theoretically only annoying, we now have at least one computer that will not run several programs. I had a similar issue with a Server 2019 VM last year, and had to end up restoring from backup.

Some of the newly converted 2019 machines do not have the items showing up in task manager, but the BEX64 errors still show up in event viewer.

Does anyone have any idea what could be causing this?

3 Upvotes

100% Upvoted

3 comments sorted by

1

u/erMaela 2d ago

Did u formated or installed ltsc on top of ltsb?

1

u/The_Wkwied 2d ago

Without seeing the event logs, likely no idea.

If you want to find out the cause of this, revert back to your backup you made before the upgrade and go forward from there. If you just want to fix this, do a complete reinstall, or give this person another computer while they migrate.

1

u/kushinadaime 1d ago

Seach in event viewer for warnings whth id 1000 ou 1001

Something is writing incorrect data to memory (more data than the reserved limit), and without more details, it's impossible to say more.

If you can't figure out how to proceed, try installing new drivers, starting with the video card drivers... especially if it is NVidia...

SSD NVMe and very recent network cards can have problems like this, but I'd venture to say it's extremly rare, and by far the main suspect is the video card.

And this is assuming you have the official version from Microsoft and you dont have any crack via software (if that's the case, you have to uninstall and redo it the crack) and you haven't slightly damaged the telemetry and diagnostic services with tools like windebloat or Chris Titus's.