Pyramix 11.1.6 Native and Windows 10 v1909

[fl]

I'm currently running Win10 version 1809 - pondering an upgrade to 1909.

Pyramix Native 11.1.6 seems to run just fine on my test machine, immediately following the 1909 install, but before I commit my main machine, I'd like a little reassurance.

Anyone experience any issues?

[Graemme]

Running 1909 on two different machines with the beta of the next version PMX 13, better known as "25th Anniversary Edition."

All is well with Ravenna ASIO and RME ASIO drivers as well as the ASIO Bridge connected to WaveLab 9.5 / Reaper 6.12

I religiously followed the Merging installation guide!

...Haven't used 11.1.6 since I was still running Windows 7, so can't directly help with this version.

1909 is MassCore tested and approved, so it's well known to the devs.

[fl]

Thanks Graemme, that's reassuring.

[Graemme]

For completeness and caution's sake, the version you are on (11.1.6) is not officially supported with Win10-1909 or even 1903. Is there any particular reason you want to update from 1809?

Pyramix Native is much less picky than MassCore as to Windows versions but it'd be a monumental PITA to have to roll back if there were issues.

Cheers,

Graemme

[fl]

Why move to 1909?

About a week ago, I discovered that my version 1809 computer was in the middle of being upgraded to Win10 version 2004, as part of Microsoft's automatic software updating. I hadn't been asked, nor did I authorize this upgrade. I managed to stop it, and removed the over 9 GB of files that had already been downloaded, and on the advice from a post on the AskWoody.com website, adjusted a Group Policy entry to make my preferred Target Feature upgrade version 2009 - with the idea that this would put off any attempt to automatically install 2004 for the time being. I have no idea how long this will delay further attempts to "upgrade" my machine. My thinking is that despite Microsoft's announcement to extend support for 1909 until November due to the pandemic, they were now going back on their word - as they do - they are now attempting to get everyone up to the latest official version whether they want it or not.

My computer has only a third generation Intel i7 processor, so I cannot use Pyramix 12 - it won't install. I am faced with the choice to either keep up with Win10 security updates, or freeze my machine at its current state with 1809, which requires a more elabourate procedure than just deferring regular updates for 30 days and Feature updates for a year, as is detailed in the Merging Knowledge Base articles about Win10 configuration. I figured that by moving to 1909, which appears to be able to run Pyramix 11 Native just fine on my test machine, I'd be able maintain things until such time as I can afford a new computer with a more recent CPU, which seems at present to be an expense I'd like to delay as long as I can.

[Graemme]

I assume that you're aware of this article on the support site:

https://confluence.merging.com/display/ ... DOWSUPDATE

This way, M$ doesn't bug me about updates...

I also subscribe to the 'AskWoody' site and I strongly suggest that Merging's now-excellent support docs site is a much better reference to rely on.

[fl]

Oh yes, I had configured my machine according to the Knowledge Base articles you cited, months ago. However, I now see that it pays to go through it every so often, looking for any changes or additions. Today, I discovered that they've added a new item found here:
https://confluence.merging.com/display/ ... jorversion
which provides a download that makes a new entry in the Registry, allowing you to specify the Target Version of Windows you wish to have - in my case, I entered 1809.

I then went back to the setting I had seen in the AskWoody site, which used the Group Policy Editor to set the

Computer Configuration\Administrative Templates\Windows Components\Windows Update\Windows Update for Business >
SelectTargetFeatureUpdateVersion

to version 2009, in order to fend off the forced upgrade to 2004, that I had encountered last week.

While this had seemed to be working, I now changed it to match the new setting made in the Registry with the Merging provided entry mentioned above, so that both are now set to 1809.

So far, I haven't seen any evidence that I'm being forced to 2004 yet, and if I understand the setting correctly, this could allow me to persist with 1809 even past its expiration date this coming November. We'll see...