Maybe a codec related issue. On Fedora, codecs need to be installed from RPM Fusion. If not, then the browser and other media players should be installed from flatpak since they come with the required codecs bundled into the product.
I don't install 'stuff'. I just update from the official repository.Viruses are GUI DPI agnostic
What problems did you have with Kaspersky? Why was the change necessary?
Certain things ran slower; I noticed this when loading web pages, and COD often didn't start right away. Kaspersky is by no means the fastest product. And you often only notice this when you uninstall it and install a lighter AV product.What problems did you have with Kaspersky? Why was the change necessary?
The problem with Kaspersky is that it does not work in 64 bits as such, it only has 64x modules, which makes it slower. And besides, it has a filter that greatly encourages your internet connection. And besides, it is 100% cpu dependent.
We completely agree with this. This has been the case with Kaspersky for a long time, and they don't really want to change it.
Are you sure that Kaspersky isn't 64-bit? Windows 11 itself only runs on 64-bit (x86-64) processors. All the critical components like file system drivers and kernel-mode services are undoubtedly native 64-bit binaries. There may be some minor 32-bit elements in superficial aspects of the software, which isn't unusual.
In Win 11 I don't know how it works, but in Win 10 it works in 32 bits with x64 modules. It is installed in the x86 folder, not the x64 one.
If the program is installed on the x86 card, it does not work in NATIVE 64 bits. Independent of the kernel and its associated modules. If it affects performance, let it work in a mixed way.Just to clarify, Kaspersky does indeed run natively on 64-bit systems. For more than a decade its core components (drivers and kernel-mode services) have been designed for 64-bit, although some auxiliary modules may still be 32-bit, which is common in complex software. The fact that it appears under Program Files (x86) doesn’t mean it’s only 32-bit; it simply indicates a mixed installation. In short: 64-bit support is complete and mature, and performance is not negatively affected.
Just to clarify, the installation path in Program Files (x86) does not define the software's actual architecture or its performance. In Kaspersky, the critical components—specifically the file system drivers and kernel-mode services—have been native 64-bit for over a decade. In fact, 64-bit Windows (10/11) would not even allow them to load otherwise.
IIRC, that has been posted on their forum before, especially the first two paragraphs, being pretty much word for word in concept.Just to clarify, the installation path in Program Files (x86) does not define the software's actual architecture or its performance. In Kaspersky, the critical components—specifically the file system drivers and kernel-mode services—have been native 64-bit for over a decade. In fact, 64-bit Windows (10/11) would not even allow them to load otherwise.
The fact that certain auxiliary modules or the UI reside in the x86 folder is simply a packaging decision common in complex software and does not affect protection or engine speed. Judging a security suite's capabilities based solely on its installation directory is a technical misconception.
If you have any doubts, you can verify this yourself: open Task Manager, go to the Details tab, right-click the headers to 'Select columns,' and check 'Platform.' You will see that Kaspersky’s core processes (like avp.exe) are running natively in 64-bit, regardless of the folder they are stored in.
If you define it by something, Windows 10 has 2 folders, one x86 and one 64x. I don't like that the antivirus works that way, because it is the only antivirus that works that way. Kaspersky does not work natively in 64-bit in Windows 10. Yes, it is more than clear to me that there are internal modules in 64-bit. Why not install it like normal antiviruses like Bitdefender, Avast and others. They are all installed in the 64-bit folder, be careful in Windows 10.Just to clarify, the installation path in Program Files (x86) does not define the software's actual architecture or its performance. In Kaspersky, the critical components—specifically the file system drivers and kernel-mode services—have been native 64-bit for over a decade. In fact, 64-bit Windows (10/11) would not even allow them to load otherwise.
The fact that certain auxiliary modules or the UI reside in the x86 folder is simply a packaging decision common in complex software and does not affect protection or engine speed. Judging a security suite's capabilities based solely on its installation directory is a technical misconception.
If you have any doubts, you can verify this yourself: open Task Manager, go to the Details tab, right-click the headers to 'Select columns,' and check 'Platform.' You will see that Kaspersky’s core processes (like avp.exe) are running natively in 64-bit, regardless of the folder they are stored in.
Even F-Secure got to that point including Windows 10, of being totally 64-bit, in Program Files.
FYI, you can install a 32-bit program in normal program files and a 64-bit program in program files x86 if the installer supports custom path. Moreover there is no 64x or x64 folder. x86 is for the 32-bit. I think it’s a good idea to do some research before posting.
Program Files (x86), but Avast is installed in the regular Program Files directory while still shipping with litany of 32-bit auxiliary binaries. They're located in a subdirectory aptly named x86.
