Anjan Nath

@Grovespaz do you by any chance have the `crc setup` logs (in your terminal buffer; as `cleanup` removes the log file) from before the issue was fixed, curious to see...

@Grovespaz tried upgrading to `2.48.0` from `2.47.0` and after `crc setup` `2.48.0` daemon was running. from your logs also it seems crc setup was installing the new daemon and there...

https://github.com/crc-org/crc/blob/25b6eb96fdf3ecb50ff8e156a8a3581b95bf5e60/pkg/crc/preflight/preflight_checks_windows.go#L160-L167 the function adding the user is also using `powershell.ExecuteAsAdmin` which should add the utf-8 BOM

Hi @moritzfl could you please try out the installer from https://github.com/crc-org/crc/actions/runs/9789510458/artifacts/1666812981 and verify if it fixes the issue, thanks!

> @anjannath seems to work fine. Thanks for the fix! thanks very much for testing it! we'll try to include this in the next release

> This could also be converted to an error, but I think that is too restrictive to the user. yes, i also think it should be a warning

closing as this cannot be solved on crc and is an issue with operator hub