Announcing Windows 10 Insider Preview Build 10166 Insider
-
OK I taxed 10166 a little with PassMark the hdd and memory I/O throughput remains significantly depreciated from Win 7 x64 while the Graphics marks are improved on the Same NTFS drive (dual boot) configuration here :
Here's a theory - I know that after an update in Windows 8.1 has completed, there's often a lot of activity for a while, due to Windows doing some housekeeping on the update files. (I think it compresses them to save space.) Could there be some housekeeping after a fresh Windows 10 install which is taking resources?
-
-
I only said to a work colleague a couple of days ago before the end of the week there will be 10166. And I was correct. What is the difference with this build…? Moreover, it is a lot more stable than 10162.
Grove Music…? It’ll grow on me I suppose.
-
You have a feedback on the start menu. You have a responsibility to report that which is not to your liking. That's what we are supposed to be doing.
Ah, I was talking about people reporting issues they observed in this build, here in this thread. Then getting criticized for doing it. Depending on what the issue was.
-
Eh, might as well switch to the fast ring again.
-
-
He can report the issue.. never said he couldn't. I just don't expect that it's going to be a high ticket item for MS to look into. Any all issues should be reported no matter how small.
Maybe I overacted a bit, but it just irked me having someone post an observation and then being told, your nit picking or that's not a show stopper. Seems to me they were basically told "why did you bother". That person likely had no idea if it was an big deal or not much of a deal. It was just an observation by them. That's all. Anyway, if I ruffled any feathers I'm sorry. I just didn't think that was fair to that member.
-
-
Maybe I overacted a bit, but it just irked me having someone post an observation and then being told, your nit picking or that's not a show stopper. Seems to me they were basically told "why did you bother". That person likely had no idea if it was an big deal or not much of a deal. It was just an observation by them. That's all. Anyway, if I ruffled any feathers I'm sorry. I just didn't think that was fair to that member.
No.. no need to apologize.. using "nit pic" was wrong on my part. I think I was trying to say that the issue was a very low level one at this phase of the OS's life cycle. MS might take it up at some point but I think they have bigger fish to fry right now. While I may not see it as an issue it might not be for others and they should report these things.. that's what the insider program is about.
Take care and have a great day!!
Jeff
-
No.. no need to apologize.. using "nit pic" was wrong on my part. I think I was trying to say that the issue was a very low level one at this phase of the OS's life cycle. MS might take it up at some point but I think they have bigger fish to fry right now. While I may not see it as an issue it might not be for others and they should report these things.. that's what the insider program is about.
Take care and have a great day!!
Jeff
Looking at some of the posts in this thread, there are bigger fish to fry. Hopefully they sort them all out, or almost all of them, by the 29th. Have a great day right back at you. I'm just about to head out the door for a nice walk in the woods with my dog Ginger. See you guys in an hour or so, take care.
-
I just noticed something that wasn't there on 10162. I left my Surface Pro 3 for about 30 minutes and went back and went to log in but the box was grayed out and I had to CAD and then logged in again.
Just sent some feedback... it didn't happen before.
My feedback...
Build 10166, Windows Logon after coming out of standby mode I noticed the text window was grayed out and I had to Ctrl Alt Delete and then log in. This was not present nor did it happen in 10162 has this been implemented as a security precausion within 10166 as it makes sense to do so, however... it should state Ctrl Alt Delete to login underneath the login window if this was the intention.
-
-
Thank you, Kari, I was looking forward to a reply for my inquiry!
I have applied the instructions and I have tried to remove the Mail&Calendar and the People app, as well. Even though Mail does not show on the list, it is still on my system and when I go to the Store it shows me that the Mail app is installed.
What am I doing wrong, please?
Below is my current full list of all native apps , AFTER applying the commands in an elevated PowerShell. This means that I opened my StartMenu, I started typing "PowerShell" and then I right-clicked on Windows PowerShell (desktop app) and "Run as Administrator"
As you can see, NO Mail there. But it still exists in my computer and Store tells me it is already installed.
Thank you.