JoKa

I'm also confused. You wouldn't need to pack `MemoryStream `into a `using`, cause the `BinaryReader `and `BinaryWriter `closes the underlying stream on `Dispose`. But both of them are instantiated with...

@refack > Is it even necessary with the call going out with `Bypass`? > [npm-windows-upgrade/src/powershell.js](https://github.com/felixrieseberg/npm-windows-upgrade/blob/39d61ffcd2696b1c714b0dfff8a4d3b24eec8641/src/powershell.js#L18) > > Line 18 in [39d61ff](/felixrieseberg/npm-windows-upgrade/commit/39d61ffcd2696b1c714b0dfff8a4d3b24eec8641) > > const args = [ '-ExecutionPolicy', 'Bypass', '-NoProfile',...

The documentation says: > "Restricted" is the default policy. So `Set-ExecutionPolicy Restricted -Scope CurrentUser -Force` should set it back to normal.

@cristianoccazinsp I had this too, after upgrading. Was triggered by calling `navigator.setOptions` inside render instead of (as shown in the docu) inside `useLayoutEffect`. Probably it's something similar in your case?

I believe it could be a similar issue, in terms of 'a warning is shown that should not, because of legacy code' but it is a different warning message and...

I am a little bit puzzled, cause IMHO devices don't have any logos. You can see the logo of the primary integration in the top right of the device page...