CrossOver Support - Community Forums

When I wanted to install a program into a new bottle today, there was a big surprise. When I install an auxiliary program like MS .NET 4.8 in a non-supported bottle, the type of bottle is overwritten. A Windows10 bottle became a Windows7 bottle.
But I found the cause of this change. The new type of bottle is written in the "Windows version" line of the file cxbottle.conf. Win7 stood there today. If this entry is deleted and the line with two semicolons is commented on, crossoverlinux reports correctly after the restart Win10 for this bottle.
I will remember this information in the file cxbottle.conf of every bottle very well.

Frank Schneider wrote:

When I wanted to install a program into a new bottle today, there was a big surprise. When I install an auxiliary program like MS .NET 4.8 in a non-supported bottle, the type of bottle is overwritten. A Windows10 bottle became a Windows7 bottle.
But I found the cause of this change. The new type of bottle is written in the "Windows version" line of the file cxbottle.conf. Win7 stood there today. If this entry is deleted and the line with two semicolons is commented on, crossoverlinux reports correctly after the restart Win10 for this bottle.
I will remember this information in the file cxbottle.conf of every bottle very well.

Good afternoon Frank.

I experienced the same in the past (I think it was the installation of MDAC2.8 at the time) and was fixing it by using the CrossOver Control Panels -> Wine Configuration, changing the Windows Version in the pop-up at the bottom of the Applications tab back to Windows 10.

Do you notice any differences / advantages with your approach?

The "Wine Configuration" setting only defines what is reported to applications and is saved in the registry, but it doesn't affect how the CrossOver UI manages bottle updates. Those are usually defined by the template set in cxbottle.conf.

I've been experiencing this problem for years. It's not just the Windows version that changes, it also assigns a new UUID to the bottle. I've told CodeWeavers about this in a ticket, but to no avail. They don't seem to care about fixing bugs, which to me is a sign that overall software quality is declining. I also see it as a security problem, since no application inside a bottle should be able to change its settings.