Updating to Windows 10 to Build 15063.13 required re-registering Waveform
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- 2505 posts since 30 Jun, 2014 from Pacific NW
Minor issue but one to note: updating Windows 10 as per the subject line seemed to cause Waveform to forget it was already registered, requiring me to re-register it with my email and password.
-
- KVRAF
- 1790 posts since 30 Dec, 2012
That's odd. Windows must have changed some of the folder IDs we use to generate the machine IDs. Hopefully this was a one off. If it happens when you update again, let us know.
-
vitocorleone123 vitocorleone123 https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=333504
- KVRAF
- Topic Starter
- 2505 posts since 30 Jun, 2014 from Pacific NW
I used the Windows Update Assistant to update to the official-but-not-full update of the "Windows Creators Update" coming on April 13th-ish. The process to update was very much like installing a new version of Windows and suppressing all the interaction pieces - it restarted my machine a couple times and applied updates before the boot menu appeared, left me with a 23GB windows.old root folder, etc.
https://www.microsoft.com/en-us/softwar ... /windows10
From what I've read, there'll be a few more "minor" updates that'll get rolled out between now and the final release, but the major update was what I installed. As such, I'm not expecting any further folder ID changes... but it is Microsoft!
https://www.microsoft.com/en-us/softwar ... /windows10
From what I've read, there'll be a few more "minor" updates that'll get rolled out between now and the final release, but the major update was what I installed. As such, I'm not expecting any further folder ID changes... but it is Microsoft!
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Ah yes, that sounds like it could well be the root of the problem. Hopefully this won't happen again any time soon.