PC not powering off/getting stuck in standby So for the last two official preview builds I've had standby/power off issues. When going into standby the PC would become unresponsive, not wake up and only a restart would fix it. Also when shutting down Windows shuts down but the hard drive stays powered on and only holding the power button down will fully shut down. I've messed around with all of the power settings, sleep, hybrid sleep, maximum performance etc, but to no avail. Any suggestions please or is this a known bug that will be addressed? I have sent it as feedback to MS.
my god it takes a very long time to install via windows update, started the download at about 1am, woke up at 7am and it still wasnt even close to being done
Don't you think something obviously went wrong? It took mine 22 minutes and I was at the desktop. And its about 5 minutes using a usb flash drive and installing clean.
It's a known issue with this build. Under certain circumstances all available language packs are downloaded and installed which takes very long.
Lads, anyone having mouse cursor freezes? been having them ever since the 10049 update...weirdly only with the touchpad (Dell Latitude E6410), it smells like a driver issue in general but why appear after build update? just wondering if anyone had a similar issue.
Does anyone think that 10049 will make it through to Slow ring? Or do you think it will be scrapped and another build will be pushed to Fast? I'm just trying to get an idea of patch support, etc. over the next few weeks. I know that 10049 has received a few patches so far. But not sure just how invested Microsoft is into this build as compared to previous builds which made it to Slow ring.
I don't think it will be in the slow rig, to old already!! Maybe within the next 48h we'll get something new, because of 2. Tuesday!!
When 10049 is patched with the updates is it still 10049 or a newer build I can see 10049 with patches hitting the slow ring as its more stable now than it was when we got it. Plus that's how I though MS was going to do this, Fast gets un-stable builds, once there stable Slow get them.
When Microsoft releases it to the Slow ring, the build will still be the same, they won't patch the .ESD downloaded. You just install updates after the installation. From what I know, the meaning of those were that ''Fast'' got the build first and ''Slow'' a week or two later.
when it's a new build the "update" will turn out in "in place upgrading" only then will u end up with a new build number