Closed oleedd closed 4 weeks ago
This occurs regardless of the use of --disable-machine-id
and --disable-encryption
switches, right?
This occurs regardless of the use of
--disable-machine-id
and--disable-encryption
switches, right?
depends on @oleedd's answer i will post some thoughts here or in separate request
With --disable-machine-id
, it started to work. Thanks. So it is solved.
Even for the initial system. It is related to the "Secure Preferences" file. Not a bug since it is a Chromium limitation.