Because anything that makes running TPM a smoother experience has to be useful. Given the controversy around TPM 2.0 – and the fact that it’ll definitely be a requirement for Windows 12 too – we can guess that this troubleshooter is likely to be something that’ll appear in the finished version of Windows 11. That’s not unusual, as with many features, Microsoft deploys them to only a small subset of testers to begin with, just to check if there are any major problems, and to monitor early feedback. Currently, we’re told that this capability is a limited rollout, so not every Canary channel tester is seeing the TPM troubleshooter. Provided, of course, this feature makes the cut for the release version of Windows 11, if it proves useful and well-received in testing. Whatever the case, having some help on-hand is certainly better than nothing (plus there’s another option here to reset your TPM back to default settings, too). Hopefully, that might give you further clues as to what’s gone awry (and maybe even solve the problem, with any luck – though Microsoft’s troubleshooters are not always that reliable). That’s not a very helpful error message, and with the new feature, what you’ll be able to do is fire up a Windows troubleshooter to look further into the issue. What might this troubleshooter actually do, then? Well, as Neowin, which spotted the tweet revealing the presence of this feature in testing, points out, it’s possible to encounter odd errors with TPM. Microsoft, however, has made it quite clear that beefing up security requires TPM 2.0, and argues that this is something implemented for the good of users, and protecting them against being exploited by hackers.Īnalysis: A handy extra to help with TPM woes (we hope)
0 kommentar(er)
