Most RecentMost ViewedMost LikesPowershell ignores NULL characters in string comparison? I stumbled across this phenomenon in Powershell 7.3.3: Turned out that $a contained a NULL character (0x00) at the end, which caused the error with ParseExact. But why does $a -eq $b return True? Solved
