Title: PowerShell ETW logging on windows needs to use a unique provider id and register the manifest. · Issue #4939 · PowerShell/PowerShell · GitHub
Open Graph Title: PowerShell ETW logging on windows needs to use a unique provider id and register the manifest. · Issue #4939 · PowerShell/PowerShell
X Title: PowerShell ETW logging on windows needs to use a unique provider id and register the manifest. · Issue #4939 · PowerShell/PowerShell
Description: Currently, PowerShell uses the same ETW provider GUID as PowerShell on Windows. This presents a few, subtle problems: 1: PowerShell 6 events cannot be easily distinguished from PowerShell/Windows. 2: PowerShell 6 is relying on a valid ET...
Open Graph Description: Currently, PowerShell uses the same ETW provider GUID as PowerShell on Windows. This presents a few, subtle problems: 1: PowerShell 6 events cannot be easily distinguished from PowerShell/Windows. ...
X Description: Currently, PowerShell uses the same ETW provider GUID as PowerShell on Windows. This presents a few, subtle problems: 1: PowerShell 6 events cannot be easily distinguished from PowerShell/Windows. ...
Opengraph URL: https://github.com/PowerShell/PowerShell/issues/4939
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"PowerShell ETW logging on windows needs to use a unique provider id and register the manifest.","articleBody":"Currently, PowerShell uses the same ETW provider GUID as PowerShell on Windows. This presents a few, subtle problems:\r\n1: PowerShell 6 events cannot be easily distinguished from PowerShell/Windows.\r\n2: PowerShell 6 is relying on a valid ETW manifest being registered to ensure events can be decoded. This assumption breaks on down-level systems that do not contain PowerShell/Windows 5.X and also ties PowerShell 6 to PowerShell/Windows events.\r\nThe solution is as follows:\r\n1: Snapshot the PowerShell/Windows ETW manifest and update the provider GUID and Provider Name.\r\n> The Event viewer location should be moved outside the Microsoft/Windows event tree since PowerShell 6 does not ship inbox.\r\n2: Provide a script or MSI action to register the PowerShell 6 manifest either at install time or as a post install, user step to address xcopy deploy use cases.\r\n3: Document the updated Provider GUID, name, and any registration steps (if appropriate)consumers.","author":{"url":"https://github.com/dantraMSFT","@type":"Person","name":"dantraMSFT"},"datePublished":"2017-09-28T17:06:45Z","url":"https://github.com/PowerShell/PowerShell/issues/4939"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:3b361298-b3f7-bdfc-80ce-ce630ecbbbc6 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 98C0:108AE3:5D2AF:81279:6AFD87B1 |
| html-safe-nonce | 8f68e9455fa6a4510103475edcfd47dc9bebf1756afb12e0c4a2b5718bb5b68b |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5OEMwOjEwOEFFMzo1RDJBRjo4MTI3OTo2QUZEODdCMSIsInZpc2l0b3JfaWQiOiI3MzEwMTE5NzU3ODk2NTgzMDkwIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 96ed55a969900a83e621354b473d7770901a596b68e7a9a9a249e679beb01f25 |
| hovercard-subject-tag | issue:261393208 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/PowerShell/PowerShell/4939/issue_layout |
| twitter:image | https://opengraph.githubassets.com/b94641b30eb5814ed699200229b8fd6a0bc578fe9b88b7066e0a5bdd22347e49/PowerShell/PowerShell/issues/4939 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/b94641b30eb5814ed699200229b8fd6a0bc578fe9b88b7066e0a5bdd22347e49/PowerShell/PowerShell/issues/4939 |
| og:image:alt | Currently, PowerShell uses the same ETW provider GUID as PowerShell on Windows. This presents a few, subtle problems: 1: PowerShell 6 events cannot be easily distinguished from PowerShell/Windows. ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | dantraMSFT |
| hostname | github.com |
| expected-hostname | github.com |
| None | bc86424ef34a73b386237872800e922d149d65ba907f63d6f150a2dcb8433bea |
| turbo-cache-control | no-preview |
| go-import | github.com/PowerShell/PowerShell git https://github.com/PowerShell/PowerShell.git |
| octolytics-dimension-user_id | 11524380 |
| octolytics-dimension-user_login | PowerShell |
| octolytics-dimension-repository_id | 49609581 |
| octolytics-dimension-repository_nwo | PowerShell/PowerShell |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 49609581 |
| octolytics-dimension-repository_network_root_nwo | PowerShell/PowerShell |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 927a6c5ab1c32b38830f1b9d3050c0b9e9aa92e1 |
| ui-target | canary-2 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width