Repository navigation
Fix kernel capture when the driver directory is missing - #426
Closed
DesolateVE wants to merge 1 commit into
Closed
DesolateVE wants to merge 1 commit into
DesolateVE wants to merge 1 commit into
Conversation
Member
|
the issue was/will be fixed in v1.21, please try it |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enabling kernel capture fails on systems where
%SystemRoot%\System32\driverdoes not exist. DebugView++ registersdbgvpp.sysat that location, but extraction does not create the parent directory. The Service Control Manager reports error 7000 (the system cannot find the path specified), followed by the UI error "Could not find the kernel messages driver device name".Create the driver's parent directory before extracting the embedded resource. Directory creation is idempotent, skips an empty parent path, and reports filesystem errors to the internal log before returning from extraction. The existing driver location is preserved.
Validation:
git diff --checkpassed.C:\Windows\System32\driverresolved kernel capture on the affected system. Runtime testing of the patched executable has not yet been performed.Maintainer question: Is the singular
System32\driverdirectory intentional to keep the capture driver separate, or should the location be the standardSystem32\driversdirectory? This fix preserves the current location pending clarification.