Cool_Tools/ExplorerPatcher
1
0
Fork 0
mirror of https://github.com/valinet/ExplorerPatcher.git synced 2025-02-17 11:08:41 +01:00
Code Releases Wiki Activity

Updated Symbols (markdown)

Valentin-Gabriel Radu 2021-11-24 13:35:12 +02:00
parent 3d5160213b
commit a97f452313
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Symbols.md

@ -45,6 +45,8 @@ If you run `22000.348.39.0` on a newer build, ExplorerPatcher will try to downlo
If it fails, ExplorerPatcher will usually work without the functionality described above as requiring symbol data and no notification will be shown in this case. Telling if you're in this mode is easy: press `Win`+`X` for example. If nothing shows, you're likely in this mode.
I usually try to update ExplorerPatcher with any necessary stuff as soon as a new stable build is pushed. Most of the times, manual intervention is not needed: bumping up the version info, or maybe hardcoding the data for this build is kind of optional, as, so long as symbols are available from Microsoft, the application always has the fallback mechanism of extracting the data from symbols available online. With Microsoft being a US-based company, symbol files and new builds are usually published during the noon/afternoon in the United States. I'm in Europe, where at that point it's usually night time, so I might be asleep, hence the delay in updating this sometimes, or maybe I just cannot do the thing at that moment. As I said, for stable builds, this should mostly be a non-issue, or at most a couple of hours without some of the functionality.
The second method you can tell what state ExplorerPatcher is in is by watching the information printed in the debug console ("Properties" - "Advanced" - "Enable console"):
* If ExplorerPatcher uses built-in symbol information, you will see some lines like the following printed at the very beginning of the console output: