windows-itpro-docs VS windows-powershell-docs

Or even https://github.com/MicrosoftDocs/windows-itpro-docs/commit/2...

Indeed, it's s simplification. If you want to go down the TPM rabbit hole, read this interesting comment about IEEE 1667: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5...

You could try Repair BDE.

Which version of wscript.exe and cscript.exe do you have? On 2021-09-14, the documentation was updated to block "un-enlightened" versions of those executables. Further, on 2021-09-21, it was updated to the correct version numbers instead of just "10.0". As a result, if you are using the latest version of the recommended block list XML, those executables should not just be outright blocked from running. Instead, as described here, the underlying script being called must be allowed by the policy otherwise the call (really the script) will be prevented.

i think https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6399 can be help you

I did find this link as well that seems to suggest that this information is no longer accurate so I want to lab this up and verify myself.

same for me, apparently this only is an issue on Windows 11 pre-releases. for me, it's build 22598.200 ni_release, do you also use windows-insider-builds? you can "fix" it by disableing driver signature enforcment in commandline and reinstalling this driver. but for this, secure boot must be disabled in the BIOS. doing this will cause valorants anti-cheat to block you from playing tho, and this is probably not the only downside of disabled secure boot... i'd love to see a fix for that, i think, they already trying as seen here.

It is because you use the -Filter parameter from Get-ADUser, which uses PowerShell Expression Language Syntax. This can cause some quirky behavior because the syntax is very strict. An interesting discussion on the topic can be found here: https://github.com/MicrosoftDocs/windows-powershell-docs/issues/180

What I'm having the most problem with is knowing where to get information. I am a moderately experienced .NET developer (Framework and Core) used to digging through Microsoft docs to figure out how to do the thing I need to accomplish. I just can't seem to find the info I need. I looked up the cmdlet reference for IISAdministration and found a far smaller set of cmdlets than WebAdministration supported. This GitHub issue tells me that Microsoft seems to have no interest in adding specific cmdlets for many tasks, preferring instead to have us interact with the ServerManager object directly. So, I pull up the docs for Get-IISServerManager which tells me how I can get an active Microsoft.Web.Administration.ServerManager object. However, there is nothing here to tell me what I can actually do to work with this object that I can find - no API, no properties, just a pitiful three examples on getting the manager, listing sites, and recycling an app pool. Five of the eight recommended articles are for WebAdministration, the module they seem to be deprecating. If I search ServerManager from the list, I find an object that has cmdlets that deal only with Windows Features and remoting. If I Google for IISAdministration info, I find lots of articles on basic site setup but not what I need, such as setting custom headers for a site. I was able to find this site which talks about web configuration but it has no documentation or examples for PowerShell. I found this page that tries to direct users to a snap-in that has been deprecated. I found this page that points users at a link for the IIS Administration API that is defunct.

Hey I know this is somewhat irrelevant to your question, but the -Filter parameter does not take a scriptblock, it actually take a string. You can refer here for more information.

Some more info here... https://github.com/MicrosoftDocs/windows-powershell-docs/issues/180

Yeah, that's not going to work because Get-ADUser's filter parameter isn't a true script block.

On the other hand, the -Filter property on the ActiveDirectory module pretends that it's a script block, but it's actually a string. It also pretends that it's Powershell syntax, but there's dozens of caveats where they work totally differently. And if you hit one of these oddball corner cases, you can easily end up with a -Filter parameter that's always true.

I followed docs, but not specs and from a few postings, the documentation seems to be wrong then: https://github.com/MicrosoftDocs/windows-powershell-docs/issues/180