On one machine (Core i5) where I had all the issues - the *only* solution was to do a clean install of Windows 10 on NEW hard drive, without the OLD recovery partitions and hidden partitions and so the recovery stuff was all ONLY Windows 10 version and that solved all my weird ass voodoo crap.Īlso out of paranoia, I found installing NA as admin, and setting to run as admin, and also logged into Windows as my Windows Store (Microsoft) account vs local account - seemed to be the trick. ) - and I suspect "anything" that uses kernel level streaming or anything which requires "ownership" permissions might cause problems with the Windows Creator Update and NI. Like the Native Access would just crash on launch, standlone apps would not launch, and same issue with certain Arturia apps (funny that the ancient E-MU software still worked. In my case, and may not impact you - the issue I had was on the Win10 machine which had been upgraded from Windows 7 to Windows 10 during the free period, and then updated to the Fall Creator Update - and then crap happened. unless you "freeze" your machine with everything working, any update may break stuff, hence good idea to learn to clone working states before updates. much like Mac OS X (MacOS) has been messing with stuff. It's mainly an issue with Windows 10 which keeps updating stuff and also messing with stuff.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |