harikovich
Advanced Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
desad79
Ответ автора
раз
Цитата: I actually did take another look at it some time ago, unfortunately, the results were inconclusive at best.
However, my personal conjecture is this:
Whenever Windows Search is performing an index/reindex of it's 'included locations', it executes an isolated host process; SearchFilterHost.exe.
This process loads, on demand, any property handler, that is required to index any of the different filetypes in the 'included locations' list.
All .NET 4 applications exposes a profiling api, allowing profilers to be attached on-the-fly.
The error you see reported in the event viewer is thrown because the initialization of this profiling api fails in IcarosPropertyHandler.
Now the reason why it fails, is most likely because the library is loaded via an unmanaged process (SearchFilterHost) (which is also loaded with very low privileges).
I'm currently not sure if something can be done about this, but at least the error itself should be benign.
There is currently two ways to avoid the error.
Either disable the Icaros property handler or remove any file locations containing Icaros' Property Filetypes (mkv, ogm, flv etc.),
from the 'included locations' list in the 'indexing options' util. |
два
Цитата: 1. Disable all Icaros Property Filetypes in IcarosConfig (this will disable the Property Handler).
2. Disable Windows Search (Indexing) in Services (if you don't use it).
3. Remove any file locations containing Icaros' Property Filetypes (mkv, ogm, flv etc.), from the 'Included locations' list in the 'Indexing options' utility.
4. Ignore the error.  |
|
Впервые вижу, чтобы кто-то напоминал об авторском праве таким странным образом 
