27.07.2015., 10:35
|
#1151
|
E Pluribus UNIX
Datum registracije: Oct 2002
Lokacija: M82
Postovi: 6,753
|
Citiraj:
Autor Mario92
Objašnjenje:
Citiraj:
File Explorer telemetry code is the cause for today's crashing so File Explorer gathers telemetry on file extensions by parsing paths (e.g. C:\foo.txt becomes txt).
An oopsie occurred, PiiSafeShellitemParsingNameProperties::LastInstanceOfChar(str, '\\') was assumed to always return valid result but for paths sans slash, you get a nullptr. e.g.: PiiSafeShellitemParsingNameProperties::LastInstanceOfChar("Foo", '\\').
Sadly that result was being passed, without checks, straight into CoTaskMemString which deferences a nullptr and blows up.
If you can't wait for a fix to KB3074681, you can mitigate a crashing Explorer with this one-liner:
(ps -n explorer | select -exp id) | % {.\windbg.exe -p $_ -c ".symfix;e SHELL32!TraceLoggingProviderEnabled+0x24 00;.detach;q"}
That's only for 64-bit targets. If you have a 32-bit machine, throw it away.
|
|
Je, samo kaj Standalone Debugging Tools moras skinuti ili samostalno ili imati WDK, a mozda bi bilo dobro napomenuti da ovo (tko ce biti dovoljno hrabar) mora pokrenuti iz elevated PowerShella.
|
|
|