Tweet
อัพถี่แท้เน้อ
-
-
ภาษาไทย อ่านเข้าใจง่าย อัพเดทComment
-
อัฟเดทวินโดว์แล้ว
อย่าลืมลบ เดี่ยวจะเปลืองที่
Comment
-
-
วินโดเมื่อก่อนที่ออก service pack นานๆออกทีนึง แต่ออกมาทีแบบว่าดีจนรู้สึกได้เลย บกบัคหายหมด แต่เดี่ยวนี้อัพเดทเป็นรายวันเลยหรอนี่ แล้วเมื่อไหร่จะนิ่งComment
-
Originally posted by wokentappy View Post
-ถึงจะอัพเดทเป็นรายวัน นิ่งช้ากว่าอัพเดทแบบทีเดียว ตรงไหนเหรอครับ?
ปลายทางเท่ากัน ต่างกันแค่ เสร็จก่อน ปล่อยให้อัพก่อน แค่นั้นเอง
บัคอะไรแก้เสร็จก็ปล่อยให้อัพเดท ดีกว่าต้องมานั่งติดบัค รอปล่อยแก้ทีเดียวซะอีกComment
-
10586.71 non-insiderComment
-
Windows 10 PC preview build 14251 now available for the Insider Fast ringComment
-
ใหม่อีกละComment
-
Windows 10 PC preview build 14251 ตัวนี้ไม่ธรรมดา
โน๊ตบุ๊ครุ่นเก่า เร็วขึ้นเห็นๆComment
-
build 14251 นี่ ไม่รู้ว่า วินโดว์ผมเน่า หรือ ว่า มัน บัคหว่า 555+Originally posted by เจ้าพ่อวินนิ่ง View Post
เปิดใช้ Lav เวลาดูหนังไม่ได้ อยากจะร้อง ... สงสัยได้ลงวินโดว์ใหม่Comment
-
นอกเรื่องครับ win 10 ซื้อ FPP มาลงถ้าเราเปลี่ยนเครื่องลงไปเรื่อยๆ มันลงได้กี่เครื่องอะครับ แบบเราอนแอคทีฟเครื่องเก่าไปลงเครื่องใหม่ไรงี้อะครับComment
-
Hi everyone,
Today, we are releasing Build 14251 Windows Insiders in the Fast ring.
Sharp-eyed Insiders likely noted the big jump in build numbers from our last preview build (11102). Historically,
the codebase for mobile had a different OS version than the codebase for PC because they were developed by different teams on different schedules.
With Windows 10, we became one Windows team and brought these two codebases together. We started by changing the version string displayed in the UI to be consistent,
which is why you saw similarly labeled builds over the past year for both Mobile and PC, but the underlying binary version numbers were still different.
As part of our work getting the common codebase ready for the next release, we decided to complete that work and sync the build numbers between mobile and PC.
Because the mobile codebase used higher build numbers than PC, we needed to jump ahead a bunch of build numbers to ensure updates to future builds will continue to work.
So that?s why build numbers went from 11105, 11106, and 11107 to 14251.
This build doesn?t have notable new features in it but I encourage you to check out the new Cortana improvements we released to Insiders earlier this week.
The January update to the Xbox Beta app for Windows 10 is also now available with some really nice improvements for Insiders to try out and give us feedback.
This build does contain some really good bug fixes that Insiders will appreciate:
?We fixed the issue where some PC games would crash switching from windowed mode to full screen,
upon game resolution change, or upon launch due to a bug in Windows graphics stack. So play your games! If you run into any issues ?
please let us know by reporting in the Feedback app and include the game title.
?We fixed the issue where applications such as Narrator, Magnifier, and third-party assistive technologies may experience intermittent issues or crashes.
?We fixed an issue where File Explorer would crash frequently when DPI settings were at 175%.
I also want to reiterate once again that with the change to release builds faster to Windows Insiders in the Fast ring,
bugs like the ones we had in the last build (or the File Explorer copy UX from the prior build) are going to pop up.
Sometimes it might be several builds before we get these bugs fixed. And there might be times where a build we release contains bugs we haven?t found in internal testing as well.
We?re at the beginning of a new development cycle for our next feature update to Windows 10,
and that means teams will be checking in lots of new code as they integrate their feature payloads.
Being an Insider means you?re getting the latest code changes, and working with new builds that are relatively new even for Microsoft employees.
If this worries you, you can switch to the Slow ring and stick with less frequent but more stable builds.
Known issues:
?You might see a WSClient.dll error dialog after logging in. We?re working on a fix for this but as a workaround,
you can run the following in Command Prompt with administrative rights: schtasks /delete /TN ?\Microsoft\Windows\WS\WSRefreshBannedAppsListTask? /F
?The Connect button does not show up in Action Center. The workaround is to press Windows key + P and then click ?Connect to a wireless display?.
?Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. The workaround is to reboot your PC.
As always ? thank you for being Windows Insiders and make sure to send us feedback on any issues you run into with this build in the Windows Feedback app.
A note on Windows 10 Mobile
I know that a lot of Windows Insiders are eager to know what?s going on with Mobile builds. As you know we?ve already released the Lumia 950, 950XL,
and 550 devices with Windows 10 preinstalled, and we?re still on track to release Windows 10 as an upgrade to existing devices early this year as we planned.
The team is working now by looking at data and reports from Insiders who have upgraded their devices to preview builds,
and ensuring that we deliver a great upgrade experience to customers. We?re excited about making the upgrade available,
and will share new information with you just as soon as we can on how the rollout will happen.
We?ve also been working on our shared core which spans across PC, Mobile, Xbox, HoloLens, and more ? which we call OneCore.
Our build systems produce new builds daily for all of these editions,
so as we?ve been doing this work we have been producing new PC builds as well as mobile builds.
Today we deliver our 4th PC preview build, and are nearly ready to start sharing new preview builds for Mobile as well.
We will start by making these builds available to devices that shipped with Windows 10 ? the 950, 950XL, and 550 ? and expand from there as we release Windows 10 to other devices.
Thanks,
gLast edited by AKK_K; 28 Jan 2016, 09:49:59.Comment
-
Comment