New
#580
See demo of new Timeline feature starting at 17:20 in video below from Windows Insider webcast.
Mixer | Interactive Livestreaming - VOD
I'd rather not have a build than have one that is behaving the way 17046 is behaving. Distressing active tasks, particularly when installing software, is not a good thing in my book.
Hey guys and gals, I wonder if one of you could try something for me as I discovered something odd.
I installled 10 Pro in a hyper-v vm without any network switch (so no internet access) and of course a local account can only be setup.
I noticed a lot of apps had the down arrows and assumed that would sort itself out when I added internet access. Now here is the odd thing - none of the 3rd party crapware stuff was listed in my menu. So no wonder the tiles had down arrows even after internet was enabled.
So I was wondering if one of you could duplicate my findings - 16299 or Insider as you prefer.
EDIT - now I am totally confused - I set up a second new vm with a local account and internet access but none if the stuff like Candy crush is anywhere to be seen.
How can this be possible?
Last edited by cereberus; 14 Dec 2017 at 18:07.
[QUOTE=Brink;1236522]See demo of new Timeline feature starting at 17:20 in video below from Windows Insider webcast.
Far better webcast quality thanks. Glad the Mouse is on the team. Will he push a build out before the end of the year?:)
Decided to spend my Windows time changing the virtualization setup.
Windows Server 2016 which was running Virtualbox and VMware is now running Hyper-V. Interestingly the Linux VMs I had created under Windows 10 were running faster under Windows Server 2016. The Windows VMs did not fare as well because most of them were created as Gen 2 and I think there was was some change between Windows 10 and Windows 2016 that did travel well. But this might not be completely the case because Windows Server IP Build 17046 is working, albeit a little slowly. I think dynamic memory is not giving it enough memory (only 512K - 640 K). The only issue with the Linux VMs was they were a bit out of date because I guess the differncing file were not carried over. This could also be a reason the Windows VMs just would not boot. Apparently I created but never started Windoiws 17046. So tomorrow I will see how Virtualbox and VMware work on Windows 10 since I removed the Hyper-V feature from those machines. I'm feeling I will be happier with this setup.
I was correct about dynamic memory. It started Windows Server IP Builld 17046 at the minimum 512K. Setting a fixed startup memory to 2GB worked much better for the only Windows VM that survived the move to Windows Server 2016. Why it didn't do this with the Linux VMs I do not know. I guess this all for posts concerning Hypler-V. Next posts will revert to Windows 10 Build 17046 which despite its problems may be with us for some time.
Need help.
See thread Intel obtane memory in
Drivers and Hardware
EDIT: Problem solved with help.
Last edited by fjk61011; 15 Dec 2017 at 15:17.