[Bug 40723] Windows NT\CurrentVersion CurrentVersion entry should change with Windows Version setting

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=40723

--- Comment #4 from Jedidiah Bartlett <jedwbartlett at gmail.com> ---
I was able to re-produce this problem again this morning after rebooting my
machine.

Steps to reproduce  (Running Stock Ubuntu Xenial 16.04:

1. From terminal, run `winecfg`
  - Edit the "Defualt Settings" to select 'Windows 7'
  - Click 'Apply'
  - Click `OK` to close the winecfg editor
2. From terminal, run `wine regedit`
  - navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion
  - Observe that ProductName has data value of 'Microsoft Windows 7'
  - Observe the error - CurrentVersion has data value of '5.0'
3. From terminal, run `winecfg`
  - Edit the "Defualt Settings" to select 'Windows 8'
  - Click 'Apply'
  - Click `OK` to close the winecfg editor
4. From terminal, run `wine regedit`
  - navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion
  - Observe that ProductName has data value of 'Microsoft Windows 8'
  - Observe the error - CurrentVersion has data value of '5.0'

HOWEVER!!
>From two separate terminal sessions, I then opened up the `winecfg` and `wine
regidit` sessions to copy-paste some screenshots to add to this bug.
When I had them opened together, I performed the following operations:
  1. In the Wine configuration dialog
    - Edit the "Defualt Settings" to select 'Windows 10'
    - Click 'Apply'
  2. In the Registry Editor dialog
    - Press 'F5' to refresh the registry view
    - Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion
    - Observe that ProductName has data value of 'Microsoft Windows 10'
    - Observe the error HAS CORRECTED ITSELF??? - CurrentVersion has data value
of '10.0'

I have since repeated this with every Windows Version option and it is working
fine.
I went back to the original steps I outlined above, and was not able to get the
bug to show itself. (Opening winecfg first, changing, closing, and then viewing
the registry).

I can no longer get the issue to re-produce now either, so something must have
been strange with my original installation.  I suggest closing this as not
reproduce able.
Thank you for the quick response and effort!

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.