rB84451f89f5c1ca84a3647da6906f95f6fe9f6c1f should also be considered for backport (discussed here rB5c01ecd2bf5d0dc0d42f90aba2a3d9f948d16bb8)

I am surprised that release 2.91 apparently does not have rB20f8130d6f905321059200756d18e9fffab60b7f (resulting in T83654)
That is a relatively old commit.

In that case, it would be good to check and backport rB20f8130d6f905321059200756d18e9fffab60b7f, rB898231fdbcc34785fefa2030bf9c17dbdedfb63f

In T83216#1074178, @Germano Cavalcante (mano-wii) wrote:

I am surprised that release 2.91 apparently does not have rB20f8130d6f905321059200756d18e9fffab60b7f (resulting in T83654)
That is a relatively old commit.

In that case, it would be good to check and backport rB20f8130d6f905321059200756d18e9fffab60b7f, rB898231fdbcc34785fefa2030bf9c17dbdedfb63f

it's developer's responsibility to commit their fix in release branch if/when they think it is safe enough to do so, at least in bcon3 (in bcon4 all commits to release branch must be reviewed and approved by a core team member first).

But we do not do cherry-picking from master into release branch typically. See https://wiki.blender.org/wiki/Process/Release_Cycle

And also, forgot that link: https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch

I would like to propose rB87b19b3aba0c: Fix: BLI_getenv returns ascii not UTF8 on windows being back ported because otherwise Cycles is broken for users with special characters in their path to the BLENDER_USER_CONFIG.

Hi could you consider backport of rBA8ca8233069579b253dcfb881200321b99e1b612c