Obviously that is not the casechk071 wrote:Note though that you NEED the updates to be able to install the big, half-yearly updates... you need a fully updated system for those, otherwise it will rather CAUSE problems, then solve those.
Windows 10 - Fall Creators update (1709) - experiences
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
-
fluffy_little_something fluffy_little_something https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=281847
- Banned
- 12880 posts since 5 Jun, 2012
The only update that won't work is the service pack 3 for my ancient Word XP. But Word works flawlessly the way it is, so I couldn't care less about that update. And now I can hide it from WU.
-
- KVRAF
- 2085 posts since 24 Jun, 2006 from London, England
Any Windows 10 Ableton users with the LoopBe Virtual Midi Driver ? Since the fall update I've had to disable the latter as it was causing BSOD whenever I launched Ableton with the stop code: BAD_POOL_HEADER
First time I think an application launch has caused a BSOD for me since probably my XP days....
First time I think an application launch has caused a BSOD for me since probably my XP days....
-
- KVRAF
- 2193 posts since 25 Dec, 2005
You don't though.I (manually) updated a computer from 1607 to 1709 without problems.Microsoft changed this with Windows 10.chk071 wrote: Note though that you NEED the updates to be able to install the big, half-yearly updates... you need a fully updated system for those, otherwise it will rather CAUSE problems, then solve those.
The Update order in Windows 7 was just horrible.
In Windows 10,parts of the OS are simply replaced that's why people have sometimes problems with new installed drivers from Microsoft.
|\/| _ o _ |\ |__ o
| |__> |(_ | \(_/_|
| |__> |(_ | \(_/_|
-
- KVRAF
- 2193 posts since 25 Dec, 2005
Did you try to re-install?mcbpete wrote:Any Windows 10 Ableton users with the LoopBe Virtual Midi Driver ? Since the fall update I've had to disable the latter as it was causing BSOD whenever I launched Ableton with the stop code: BAD_POOL_HEADER
First time I think an application launch has caused a BSOD for me since probably my XP days....
|\/| _ o _ |\ |__ o
| |__> |(_ | \(_/_|
| |__> |(_ | \(_/_|
-
- KVRAF
- 2085 posts since 24 Jun, 2006 from London, England
I only use LoopBe for LKBridge/UBridge which I super rarely use so I've just uninstalled it for the time being.
-
- KVRAF
- 2008 posts since 11 Aug, 2012 from omfr morf form romf frmo
No problems here. BAD_POOL_HEADER usually indicates a RAM or driver issue. Try reinstalling LoopBe. If that doesn't work reinstall Ableton.mcbpete wrote:Any Windows 10 Ableton users with the LoopBe Virtual Midi Driver ? Since the fall update I've had to disable the latter as it was causing BSOD whenever I launched Ableton with the stop code: BAD_POOL_HEADER
- KVRAF
- 7137 posts since 8 Feb, 2003 from London, UK
I had a big batch of updates come through last week then last night got 1709 (I like the way Microsoft now follows the Ubuntu version numbering scheme...). So far, apart from its consistently annoying habit of replacing my desktop background image and losing several file explorer preferences, I've not seen any problems. I've started and tested Reaper with my full drumkit load (~30Gb now...) and MuLab and both still work.
(At some point my Echo AudioFire ASIO driver will no longer work for Reaper, either, I'm sure... ASIO4All is currently rescuing MuLab and Stagelight. This seems to be down to what the application builder rebuilds, rather than the OS, though, so it'll depend on when something breaks in the library code for Reaper, I guess.)
(At some point my Echo AudioFire ASIO driver will no longer work for Reaper, either, I'm sure... ASIO4All is currently rescuing MuLab and Stagelight. This seems to be down to what the application builder rebuilds, rather than the OS, though, so it'll depend on when something breaks in the library code for Reaper, I guess.)
-
- KVRist
- 381 posts since 28 Oct, 2002
Every thing works here except I lost my 2nd monitor until I "restarted" then it would work until I booted up again. I then turned fast load off in power settings to see if that helped and it works fine now.
-
- KVRian
- 851 posts since 26 Jan, 2014 from United States of America
Had issues here.
I updated on Day One. I have 2017 computer, kaby lake, so it was new enough to start downloading update soon as I used Check for Updates function. I lost internet when it was at about 30% downloaded (the entire network- all computers) so it was sitting there for a while, then Internet came back and it finished downloading and installing.
The first major problem was that computer would not shut down- instead, it would go to Log Off and come back to Log In screen. It felt like Buttons Settings got massed up- it also would not sleep- also this computer was set to Sleep Never, but manual Sleep at Start button did not work. I found out that Fast Boot some how got enabled in Windows.
There is Fast Boot in BIOS- I had it disabled. I thought I did not have fast Boot enabled, but when i checked settings- it was enabled! So I disabled it and it solved the problem.
I had Start button not working for short time- Press Start would make Nothing happen- would take many clicks for Start to open. Solved after few restarts.
I had to reauthorize Omnisphere and Addictive Drums and Keys.
I updated on Day One. I have 2017 computer, kaby lake, so it was new enough to start downloading update soon as I used Check for Updates function. I lost internet when it was at about 30% downloaded (the entire network- all computers) so it was sitting there for a while, then Internet came back and it finished downloading and installing.
The first major problem was that computer would not shut down- instead, it would go to Log Off and come back to Log In screen. It felt like Buttons Settings got massed up- it also would not sleep- also this computer was set to Sleep Never, but manual Sleep at Start button did not work. I found out that Fast Boot some how got enabled in Windows.
There is Fast Boot in BIOS- I had it disabled. I thought I did not have fast Boot enabled, but when i checked settings- it was enabled! So I disabled it and it solved the problem.
I had Start button not working for short time- Press Start would make Nothing happen- would take many clicks for Start to open. Solved after few restarts.
I had to reauthorize Omnisphere and Addictive Drums and Keys.
- KVRist
- 67 posts since 4 Nov, 2017 from Canada
No problems here. Is Microsoft edge good now?
-
- KVRist
- 211 posts since 8 Dec, 2006 from Germany
Works after fixing the following issues:
- re-authorize Addictive Keys
- re-installation of ASIO & Patchmix Software for E-MU 0404 PCIe
- re-authorize Addictive Keys
- re-installation of ASIO & Patchmix Software for E-MU 0404 PCIe
-
original flipper original flipper https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=8999
- KVRAF
- 2541 posts since 14 Sep, 2003 from Essex
Hi
Just curious - I am still on WinXP!!!
How much disc space (roughly) does Win10 (including this latest 1709 update) take up?
Many thanks
Just curious - I am still on WinXP!!!
How much disc space (roughly) does Win10 (including this latest 1709 update) take up?
Many thanks