After KBKB5037771 (Windows 11) two start-up programs have Security Warnings

Topic

New Reply

Yesterday I installed KBKB5037771 on my 23H2 Windows 11 Pro desktop, which uses ESET Internet Security.

Now, each time I boot, two programs  in the common start-up throw security warnings.  As you can see from the  attachments, both are called by LNK files:

* The first is a portable EXE file that allows me to minimise a running program to the system tray — I have been using it for some time.

* The second is a four-line BAT file that I wrote using standard CMD commands.

This has never happened before.  I tried running them after boot (first shutting down RBTray using Task Manager), and then they do NOT throw warnings.  I tried running other portable EXE files on the PC, and again, there were no warnings.

So it only seems to be happening on boot, and it is also not happening to some other BAT and EXE files that are set to run at boot via LNK files.  Neither the EXE nor the BAT has any ADS files attached.

QUESTIONS: First, why is this happening?  That’s probably too difficult, given all the complications of M$’s recent updates.

Secondly, I don’t want to turn off all file blocking.  How can I unblock just these two files?  As you can see, there are no checkboxes on either one.

Reply | Quote

Replies

Both files are not digitally signed.
My guess is that this https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30050 which is part of the update is triggering the issue. Question? That appears to be calling from a d:\ outside of the c:\windows location. What if you tried moving that to the c drive?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Dear Susan,

Solved!  Thank you very much!  And thank you for reading CVEs whose significance I would not understand.

On my relatively new PC, I decided that instead of partitioning the 1TB drive , I would create a subdirectory C:\@Data for everything on my earlier D: drive.  Then I used Visual Subst from NTWind to substitute D: for C:\@Data  permanently.

After reading your reply, I opened the Properties windows of both LNK files, and changed D:\ to C:\@Data\  in the Target: and Start in: fields.  When I rebooted, the problem was fixed — no more warnings.

I then checked the other LNK files that I had written in both Start-ups,  and found that I had used C:\@Data\  instead of D:\ , so that is why they did not also trigger warnings.

There have been just a couple of earlier issues where I had to change paths from D:\ to C:\@Data\ to make things work.  I now have another such issue — and I am kicking myself for forgetting about the substitute drive and writing my post.

Reply | Quote