14251更新公告说明

csd1259

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,   
g

csd1259

修复——

这个版本确实包含了一些非常好的错误修正，业内人士将体验到：

•我们修复了——一些PC游戏会崩溃从窗口模式切换到全屏，在游戏分辨率的变化，或因在Windows图形堆栈错误发射。所以玩你的游戏！如果你遇到任何问题，请让我们知道通过在反馈应用程序的报告，包括游戏名称。

•修复了——应用如旁白，放大镜，和第三方辅助技术可能会遇到间歇性问题或崩溃。

•修正了——文件浏览器会崩溃经常在DPI设置为175%。

已知bug——

已知问题：

•你可以登录后看到一个wsclient.dll错误对话框。我们正努力修复这可作为一种替代方法，您可以在命令提示符下运行行政权如下：schtasks /delete /TN “\Microsoft\Windows\WS\WSRefreshBannedAppsListTask” /F

在行动中心的连接按钮不显示。解决方法是按下Windows键+ P，然后单击“连接到一个无线显示”。

由于最近的内存管理变化，您可能会看到周期性应用程序崩溃或其他内存相关的应用程序错误。解决方法是重新启动你的电脑。

以上为机翻，勿喷

感觉没啥大的变化，相对于11102

tittys3000

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,   
g
---------------------------------
嗨，大家好，
今天，我们发布构建14251的Windows有业内人士在快速环。
眼尖的业内人士可能会注意到，在版本号的大跳跃，从我们过去的预览版本（11102）。从历史上看，该代码库的移动产生了不同的操作系统版本比代码库的电脑，因为它们是由不同的时间表针对不同的团队开发的。在Windows 10中，我们成了一台Windows团队并带来了这两个代码库一起。我们开始通过改变显示在用户界面是一致的版本字符串，这就是为什么你看到类似标记建立在过去一年中为移动和PC，但潜在的二进制版本号仍然不同。由于我们的工作得到了共同的代码库准备好了下一个版本的一部分，我们决定完成这项工作，并同步手机和PC之间的版本号。由于采用更高的移动代码库比PC内部版本号，我们需要跳跃前进一串版本号，以确保更新将来的版本将继续工作。所以这就是为什么内部版本号就从11105，11106和11107至14251。

此版本没有在其显着的新功能，但我鼓励你检查出新的柯塔娜改进我们发布了业内人士本周早些时候。一月份更新到Xbox测试版应用程序的Windows 10现在也可以用一些非常好的改进业内人士尝试，并反馈给我们。

此版本确实包含了一些非常好的bug修复的业内人士将欣赏：
我们固定的问题，一些PC游戏会崩溃，从窗口模式切换到全屏，在游戏分辨率的变化，或经推出，由于在Windows图形堆栈中的错误。所以，玩你的游戏！如果您遇到任何问题 - 请让我们知道通过在应用程序的反馈报告，其中包括了游戏标题。
我们固定在那里的应用，如讲述人，放大镜，和第三方辅助技术可能会遇到间歇性问题或崩溃的问题。
我们修正了一个文件资源管理器经常会崩溃，当DPI设置为175％。

我也想再次强调的变更发布版本更快的Windows有业内人士在快速环，就像那些我们曾在上次生成错误（或文件管理器复制UX从先前版本）重申要弹出。有时它可能是几个建立之前，我们得到这些错误修复。而有可能是时间，我们发布一个版本包含我们还没有发现在内部测试和错误。
我们正处于一个新的发展周期，为下一个功能更新到Windows 10的开始，这意味着球队将在很多新的代码检查，因为他们自己的集成功能的有效载荷。作为一个知情人意味着你得到最新的代码修改，并与新的工作建立是相对较新的甚至是微软的员工。如果你担心，你可以切换到慢环，并坚持那么频繁，但更稳定的版本。

已知的问题：
登录后，您可能会看到一个WSClient.dll错误对话框，我们正在努力修复了这一点，但作为一种替代方法，您可以运行下面的命令提示符管理权限：schtasks的/删除/ TN“\微软\的Windows \ WS \ WSRefreshBannedAppsListTask“/˚F
连接按钮不会在操作中心显示出来。解决方法是按Windows键+ P，然后单击“连接到无线显示”。
由于最近内存管理的变化，你可能会看到周期性的应用程序崩溃或其他存储相关的应用程序错误。解决方法是重新启动您的计算机。
与往常一样 - 谢谢你作为视窗业内人士，并确保向我们反馈您在使用此版本的Windows反馈应用程序的任何问题。

在Windows 10手机的注意事项我知道很多的Windows业内人士都急切地想知道发生了什么事情与移动基础之上。如你所知，我们已经发布了的Lumia 950，950XL和550设备与Windows 10预装，而且我们仍有望发布Windows 10作为升级到今年年初，我们计划现有设备。该小组目前工作通过观察数据和谁升级他们的设备有业内人士报告预览版本，并确保我们提供一个很大的升级体验的客户。我们很高兴能够让升级可用，并会与你刚才只要我们可以共享的推出将如何发生的新信息。
我们也一直致力于我们共同的核心它横跨PC，手机，的Xbox，HoloLens，等等 - 我们称之为OneCore。我们构建系统每天产生新版本，所有这些版本，从而我们一直在做这项工作，我们一直在生产新的PC建立以及移动的基础之上。今天，我们提供了4 PC预览版本，并几乎准备好开始分享新预览版的手机也是如此。 950，950XL和550 - - 并从那里扩大，因为我们发布Windows 10到其他设备，我们将通过这些构建提供给附带Windows 10设备启动。
谢谢，
G

csd1259

csd1259

tittys3000 发表于 2016-1-28 08:24
Hi everyone,
Today, we are releasing Build 14251 Windows Insiders in the Fast ring.
Sharp-eyed I ...

同机翻

zzkzzz_001

修复了一些问题

dsazx

太好了，游戏全屏修复了

dzh9988620

支持个了。