• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Windows 10 End of Support 10/25

Still trying to get my PC to enrol in ESU.

Anyone know what ESUEligibility = 0x7 and ESUEligibilityResult = 0x9 mean? These values are not listed in the tables of codes that I can see online
 
If I follow the methods online I can set the values in registry to 2 and 1 respectively, then I do get an Enrol button in WU, but when I click Enrol then Next I just get
1760264821434.png
which is kinda not helpful
 
URGH, typical - I hate technology 🤬 for no apparent reason, my PC is suddenly now enrolled in ESU :rolleyes:

Sorry, this is my non-DAW machine we're talking about - I just came here because I knew this is a place where I'd get helpful replies :love:

All I can say is I'm glad writing music is easy compared to dealing with online tech stuff!
 
And I'm back :rolleyes:

Since my last message, I am again getting 0x7 and 0x9

Before, it looked like a Search for Updates in WU resets the two values in the registry. I was automatically looking for updates in WU, and a search happened some time after my last message - and so the two values appear to have been reset by that, and I am no longer getting the You are Enrolled message in WU
 
Before, it looked like a Search for Updates in WU resets the two values in the registry. I was automatically looking for updates in WU, and a search happened some time after my last message - and so the two values appear to have been reset by that, and I am no longer getting the You are Enrolled message in WU

What exact OS are you running? Your signature says one thing - and this thread says another.

And - walk thru this to ensure you meet all requirements:


VP
 
Last edited:
Hi VP

Apologies, this is on my non-DAW machine, which is Windows 10 Home - it's fully updated, and as far as I can see, all prerequites are met. I'll work my way through the above, thanks

EDIT: the problem is I'm getting the two values 7 and 9 for ESUEligibility and ESUEligibilityResult which do not appear to be documented that I can find - these prevent the Enroll button appearing so I can't even get as far as the unable to enroll problem

I was able to get the Unable to enroll problem because I set those registry values to 2 and 1 repectively - that allowed the Enroll button to appear
 
Last edited:
OK, you'll be glad to hear that this is the end of this affair. FYI values of 7 and 9 mean my PC is a commercial migrated device, whatever that means. I found the full list of values in AskWoody forum:
1760337390223.png


What it does mean is no (free) ESU for me unless I faff around with buying licenses and so forth, so I'm biting the bullet and looking to buy a new PC :rolleyes:

Thanks for help, all
 
Well, after not seeing any option for me to enter the Win10 EOS extension program offered by the Windows Update utility, and having already resolved to suck it up and install Win11 even though I don't have a care in the world using Win10, for whatever reason I chose to install available updates yesterday, November 16, even though I let things lapse on October 14, the supposed official cutoff date. Then, lo and behold, the option to enter EOS arrangements appeared and became available. I needed to spend a few minutes sorting out my Microsoft login—which I'd avoided using since I didn't want to let them near my data as in migrating it to their data cloud—and it wasn't even for the $35 paid option, it was for the totally free option.

There were other factors at play. First, two days ago, much to my own surprise, I left Guitar Center with a Black Friday sale Fender Player II Stratocaster that was one of those rare perfect factory setup guitars with a neck that fit my fretting hand perfectly—unlike the hundreds of Strats I've auditioned over the past months from $300 Squiers to $7,000 Custom Shop examples. The $699 I paid was approximately the same amount I was prepared to pay for two new NVME SSDs and a new interface (for instance Yamaha URXC-44) to replace my firewire interface that's in the "threatened" category, which may or may not have worked in Win11. All of a sudden, here was a chance to offset that unusually emotional guitar purchase.

Also, one of few reasons that would have enticed me to make major changes—the imminent rollout of MIDI 2—seems like it's not going to happen until till at least Q1 next year, and software and hardware manufacturers will need time to react, so I wasn't going to get MIDI 2 (which requires Win11) even after all the labor I'd have to put into a Win11 fresh install (don't want to risk installing over the present version, thanks, even though I understand some have no problems).

Now that the dust's settled, out of the blue I now own a very useful instrument and I just saved like a week's worth of PC transitions not to mention the chunk of change on new Win 11 hardware, allowing me to spend the same energy on recording a big production instead of making a big production out of PC changes. Sure, I'll still have to deal with Win11 eventually, that's not going away, but at least in the short term, I'll get a lot more out of having a guitar I can play effortlessly than Win11.
 
There were other factors at play. First, two days ago, much to my own surprise, I left Guitar Center with a Black Friday sale Fender Player II Stratocaster that was one of those rare perfect factory setup guitars with a neck that fit my fretting hand perfectly—unlike the hundreds of Strats I've auditioned over the past months from $300 Squiers to $7,000 Custom Shop examples. The $699 I paid was approximately the same amount I was prepared to pay for two new NVME SSDs and a new interface (for instance Yamaha URXC-44) to replace my firewire interface that's in the "threatened" category, which may or may not have worked in Win11. All of a sudden, here was a chance to offset that unusually emotional guitar purchase.
Sounds like a win to me!

Wouldn't be too worried about MIDI 2.0 support, it's designed as much as possible from the ground up to be platform-agnostic.

Even if MS doesn't backport compatibility to W10, all you'll likely need is a driver/firmware download for your machine for the hardware in question, which is kind of the whole point of an open-ended development OS like Windows, even if you wouldn't know it by looking at the MS's recent dev cycle.
 
Sounds like a win to me!

Wouldn't be too worried about MIDI 2.0 support, it's designed as much as possible from the ground up to be platform-agnostic.

Even if MS doesn't backport compatibility to W10, all you'll likely need is a driver/firmware download for your machine for the hardware in question, which is kind of the whole point of an open-ended development OS like Windows, even if you wouldn't know it by looking at the MS's recent dev cycle.
Appreciate the validation of the strategy I pretty much stumbled into, thanks, though I'm a little confused by some of your OS comments. First off, I never mentioned considering switching to Mac, so your statement about platform-agnostic went over my head. Same with the one about "an open-ended development OS like Windows"—isn't the open-ended development OS Linux, not Windows? Lastly, MIDI 2.0 is definitely not going to be backported to Win10. What am I missing? :)
 
Well, after not seeing any option for me to enter the Win10 EOS extension program offered by the Windows Update utility, and having already resolved to suck it up and install Win11 even though I don't have a care in the world using Win10, for whatever reason I chose to install available updates yesterday, November 16, even though I let things lapse on October 14, the supposed official cutoff date. Then, lo and behold, the option to enter EOS arrangements appeared and became available. I needed to spend a few minutes sorting out my Microsoft login—which I'd avoided using since I didn't want to let them near my data as in migrating it to their data cloud—and it wasn't even for the $35 paid option, it was for the totally free option.

There were other factors at play. First, two days ago, much to my own surprise, I left Guitar Center with a Black Friday sale Fender Player II Stratocaster that was one of those rare perfect factory setup guitars with a neck that fit my fretting hand perfectly—unlike the hundreds of Strats I've auditioned over the past months from $300 Squiers to $7,000 Custom Shop examples. The $699 I paid was approximately the same amount I was prepared to pay for two new NVME SSDs and a new interface (for instance Yamaha URXC-44) to replace my firewire interface that's in the "threatened" category, which may or may not have worked in Win11. All of a sudden, here was a chance to offset that unusually emotional guitar purchase.

Also, one of few reasons that would have enticed me to make major changes—the imminent rollout of MIDI 2—seems like it's not going to happen until till at least Q1 next year, and software and hardware manufacturers will need time to react, so I wasn't going to get MIDI 2 (which requires Win11) even after all the labor I'd have to put into a Win11 fresh install (don't want to risk installing over the present version, thanks, even though I understand some have no problems).

Now that the dust's settled, out of the blue I now own a very useful instrument and I just saved like a week's worth of PC transitions not to mention the chunk of change on new Win 11 hardware, allowing me to spend the same energy on recording a big production instead of making a big production out of PC changes. Sure, I'll still have to deal with Win11 eventually, that's not going away, but at least in the short term, I'll get a lot more out of having a guitar I can play effortlessly than Win11.
And your guitar will never require updates, go obsolete or require a full reinstall.
 
Appreciate the validation of the strategy I pretty much stumbled into, thanks, though I'm a little confused by some of your OS comments. First off, I never mentioned considering switching to Mac, so your statement about platform-agnostic went over my head. Same with the one about "an open-ended development OS like Windows"—isn't the open-ended development OS Linux, not Windows? Lastly, MIDI 2.0 is definitely not going to be backported to Win10. What am I missing? :)

I'm comparing Windows to Mac basically in calling it open-ended, because practically anyone can write a Windows driver for some unsupported piece of hardware to make it PnP.

The Apple ecosystem is just really strict with driver signing and is less dev friendly in general for third party hardware support, to say nothing of hardware... which is orders of magnitude more restrictive.

Pros and cons to such a secure OS environment for sure, but being small dev-friendly isn't one of them, such as the ones that will be working on Midi2 hardware support for Windows with little controllers and such devices, although MAC will 100% support MIDI2 natively so again it won't be an issue.

Don't think I implied you wanted to switch to iOS? 'Platform-agnostic' just stresses that regardless of what operating system you're on, the protocol still works...
 
And your guitar will never require updates, go obsolete or require a full reinstall.
One reason I like to have keyboard workstation around as well as all the software.
 
I'm comparing Windows to Mac basically in calling it open-ended, because practically anyone can write a Windows driver for some unsupported piece of hardware to make it PnP.

The Apple ecosystem is just really strict with driver signing and is less dev friendly in general for third party hardware support, to say nothing of hardware... which is orders of magnitude more restrictive.

Pros and cons to such a secure OS environment for sure, but being small dev-friendly isn't one of them, such as the ones that will be working on Midi2 hardware support for Windows with little controllers and such devices, although MAC will 100% support MIDI2 natively so again it won't be an issue.

Don't think I implied you wanted to switch to iOS? 'Platform-agnostic' just stresses that regardless of what operating system you're on, the protocol still works...
Got it. One of these days I'll install on the M1 Mac laptop I have that I've never used for music.
 
Back
Top