P: I'd like to know how to disable the startup tutorial about generative ai

@Secret Jardin Marketing Thanks for your very detailed message, it is helpful to people who don't know about how softwares work. However I am also a programmer and this problem can have multiple solutions. And i'm very right to be angry about it because they are a big company with a lot of engineers and we are paying a lot of money monthly for them to make things work. He are some solutions to make things easier for everyone:
1 - They can disable this tutorial until they can solve the problem with their own ways
2 - They don't have to check for our actual name because i'm assuming we have some ASCII compatible user ids in their databases because everything else works fine so they can use that one for checking
3 - On their saved data they can instead use only a boolean (True-False) for saving the tutorial pass check without any further checks for other user names (and they can just turn it to false again if the user logs out assuming they want every new user to see the tutorial)
4 - They can add a basic option in the settings to turn off this tutorial check, this way we don't have to wait for adobe to fix this issue
5 - They can switch to a better save data structure as ASCII character problem is a problem of 10 even 20 years ago and they are a very big company that should think about these kinds of things and prepare even before an issue comes up
6 - If they can't change their save data structure, they can just add a second save file that does support ASCII characters with their new features
7 - They also should check for any issues and bugs BEFORE they release a broken update 4 times, to prevent any further issues.

Just one more thing: has anyone read an official statement from ADOBE about this annoying problem? Does ADOBE want a solution to this?

A good explanation for this problem that makes most people 'angry'.
I believe that with ADOBE's structure and the technology acquired after years of developing the application, the will to solve the problem is lacking!!!
Hugs from Brazil

Bonjour, 

merci pour cette réponse claire, c'est apprécié. Je m'en vais regarder tout cela. 

clément 

Enough already! I'm fed up! Someone, please solve this problem!

@Umut Çakmak To be fair, I do tend to side with developers here when people say "it shouldn't be so hard to fix", because really, there's ALWAYS some repercussions to changing processes, and as a user, you wouldn't necessarilly see all that implies under the hood.

What's obviously going on here is a character encoding issue, where our names are using characters which fall outside of the ASCII/ISO 8859 Latin-1 table. In the past, different languages would use different (but also limited) selections of characters, which matched different glyphs to the same limited 256 table (one byte per character). When moving the binary data to a system using a different norm, these would be represented using the incorrect glyphs a they get converted the other way around. In recent years, most systems have shifted to using UTF-8, which has a wide enough range of glyphs to encompass everything used in every language (so far), one table for all, if you will but this relies on using more bytes for characters outside the ASCII range, which remains the base and norm. Whenever a bit of code which is still working with one-byte ASCII encoding encounters these multi-byte character, it doesn't know how to group them and interpret them correctly, so it just handles each individual byte as if they were all individual characters.

You could say "OK, let's just change the code so that it reads the data as UTF-8", sure, but what if that bit of code passes on to another bit of code which still expects ASCII? "OK, we'll change that one too then", OK, but what if that other bit of code causes some memory allocation issues because it now has to deal with variable-length data? "OK, let's fix that", and it goes on and on and on.

What I'm trying to say here is that what seems like a simple bug might require fundamental changes in several processes in order to fix, and we just don't know that. The only thing I'm hoping is that Adobe doesn't just decide "This is too much work, forget it"

So, because i have a non-american letter in my name, photoshop still thinks i should be punished in version 25.4. This shouldn't be such a hard thing to fix guys...

No, I updated to see if that will fix the problem, but no.

Once again disappointed with ADOBE!
Today I updated to WEB version 25.4.0 and that 'Generative Fill Wizard' has not been fixed.
I've also corrected 'characters outside the ASCII table', in my case: João to Joao and nothing has changed!!!
Now if I want to get rid of this annoying video I'll have to downgrade to version 25.0! And the worst thing is that I'm a subscriber (I spend my money) and I still have to be annoyed every time I start PS.
Disappointed!

I'm very dissapointed. I have the same issue. But this is not the only one problem with my PS.

I can't print. Just trying to open printing window (doesn't matter if I click ctrl+p or menu -> print), and PS crashes all the time. Can't find issue for turning off AI tutorial and for disable printing as well.

Using Adobe programs from years and it getting worse year by year. Just had to express my frustration.