Mobile and Desktop Processors
Intel® Core™ processors, Intel Atom® processors, tools, and utilities
16770 Discussions

IDSAUpdate attempts to access a protected folder

DOCDJ
Beginner
730 Views

I am not sure if this is the proper forum for my problem. I could not find one that was a good match. If I am in the wrong one, can someone tell me the correct forum?

Starting yesterday (June 11, 2025), I am getting dozens of attempts to access a protected folder by programs having names starting with IDSAUpdate. The attempts are being blocked by Windows Protected Folder Access. Which I always keep on. The folder is %common_appdata%\Microsoft\NetFramework\BreadcrumbStore\

I keep permitting it, but each time the name of the program has a slightly different ending. For example: IDSAUpdatecmrvqv33.exe

I am spending a lot of time creating permissions for these programs and am now suspicious of them.

Are these attempts valid and how can I stop them?

0 Kudos
1 Solution
pressed_for_time
Valued Contributor II
665 Views

There is a utility from Intel that will uninstall IDSA, it can be downloaded from here .

View solution in original post

0 Kudos
5 Replies
pressed_for_time
Valued Contributor II
696 Views

This could be Intel Driver & Support Assistant (IDSA) checking for updates, if you have it installed. Windows should recognize it as a "friendly" app and let it through Controlled Folder Access automatically. It might be worth configuring this manually to see if it makes any difference.

0 Kudos
DOCDJ
Beginner
672 Views

The problem is that IDSA creates a new a-named app for EVERY access. I counted at least 20 different attempts that had to be OK'd before I got fed up and blocked them all. Since I don't have any Intel drives, I don't know why I even have IDSA on my system.

0 Kudos
pressed_for_time
Valued Contributor II
666 Views

There is a utility from Intel that will uninstall IDSA, it can be downloaded from here .

0 Kudos
DOCDJ
Beginner
616 Views
0 Kudos
DOCDJ
Beginner
671 Views

PS. ALL the attempts were for the SAME folder. It seems that IDSA is spawning individual processes for each "thing" it needs to do. 

0 Kudos
Reply