I agree that this problem is annoying. But honestly I have no idea
why that happens for some people. I have never seen that error
happening for me. I assume that the problem depends on the location
where the user plug-ins are installed. On my office PC (no admin
privileges for me), the plug-ins are installed into "c:\Users
2_2106435170_win32_win32_x86_64\plugins\". That is a folder that I
certainly can write to. Maybe that the user plug-ins go into "c:
\Program Files\IBM\SDPShared\" for users who have that problem.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.