Comments on: Crash course on authoring Windows 7 Troubleshooting Packs

By: Das nächste Windows - frontier to insanity

Das nächste Windows - frontier to insanity — Wed, 31 Dec 1969 18:00:00 +0000

[...] an, die zwar von Microsoft, aber sonst noch von keinem anderen Anbieter verwendet werden. (Hey, das basiert auf PowerShell-Skripten! Macht es euch zu Nutzen und erfreut den Anwender mit noch einfacheren Problemlösungen, ihr [...]

By: Cleveland Windows 7 Launch Event « {get; set;} : CODE

Cleveland Windows 7 Launch Event « {get; set;} : CODE — Wed, 31 Dec 1969 18:00:00 +0000

[...] This is more cool stuff for reducing those pesky support costs. The presenter demoed an issue where there was no sound coming from his laptop. He ran the Audio Troubleshooter, and it unmuted his audio for him. You can write your own packs, which are simply collections of Powershell scripts held together with an XML manifest. You can pack them into a singed CAB file and distribute them with application installers or over the web. I found a great crash course here. [...]

By: Dan

Dan — Wed, 31 Dec 1969 18:00:00 +0000

How can i add the troubleshooting pack i made to action center?

By: Keith Hill

Keith Hill — Wed, 31 Dec 1969 18:00:00 +0000

Vejay, you need to enable script execution in PowerShell. Run PowerShell elevated (as admin) then execute:

PS> Set-ExecutionPolicy RemoteSigned

By: at Digital Bangladesh

at Digital Bangladesh — Wed, 31 Dec 1969 18:00:00 +0000

[...] These fix common problems, check for incorrect settings, clean up your PC and more. Developers can create additional troubleshooters, too. You can read more about that at Within Windows. [...]