@abbaccadd0 said in Kaspersky\VPN\KSOS 21.24.1.128 MR24!:

Kaspersky crashes on the path selection interface in Windows 11 Build 28000.
This appears to be caused by an outdated version of MSVCP140.dll. I know this is a preview system, and many other programs on the computer are also experiencing this issue.
Other software can resolve path selection by replacing the system's MSVCP140.dll, but Kaspersky clearly won't allow itself to run if critical DLLs are swapped out.
Using certain forced file deletion tools can temporarily restore Kaspersky's path selection UI, but eventually Kaspersky will become completely unusable.

BTW, I mean, I REALLY KNOW this Windows is a INSIDER VERSION.

Application: avpui.exe
CoreCLR Version: 8.0.1225.17001
.NET Version: 8.0.12-kl.7.9.753.0
Description: The process was terminated due to an unhandled exception.
Stack:
at KasperskyLab.UI.Framework.NativeMethods.Api.Shell32.Shell32Dll.SHGetFileInfo(IntPtr, KasperskyLab.UI.Framework.NativeMethods.Api.Kernel32.Enums.FileAttributeFlags, KasperskyLab.UI.Framework.NativeMethods.Api.Shell32.Structs.ShFileInfo ByRef, Int32, KasperskyLab.UI.Framework.NativeMethods.Api.Shell32.Enums.ShGetFileInfoFlags)
at KasperskyLab.UI.Platform.Views.PathBrowsing.Native.NativeShellMethodsWrapper.GetShellFileInfo(KasperskyLab.UI.Platform.Views.PathBrowsing.Native.ComPtr, KasperskyLab.UI.Framework.NativeMethods.Api.Shell32.Enums.ShGetFileInfoFlags)
at KasperskyLab.UI.Platform.Views.PathBrowsing.Native.FileSystemEntryInfoProvider.GetFileInfo(KasperskyLab.UI.Platform.Views.PathBrowsing.Native.ComPtr)
at KasperskyLab.UI.Platform.Views.PathBrowsing.Native.FileSystemEntryInfoProvider+<>c__DisplayClass10_0.<EnumerateShellFolderByChunks>b__0()
at KasperskyLab.UI.Core.Threading.DedicatedStaThreadExecutor+<>c__DisplayClass2_0`1[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].<Execute>b__0()
at KasperskyLab.UI.Core.Threading.DedicatedStaThreadExecutor.ThreadFunction(System.Object)
at System.Threading.Thread+StartHelper.Callback(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.Thread.StartCallback()

Hi, abbaccadd0.
Changing or replacing MSVCP140.dll is restricted by security risks.
I am discussing with developers. It depends from some our internal processes and plans for updating libraries.
I will return to you with an answer later with result what we can to do with this.

Andrey Lexikov