Hi all, First, to new people: welcome to Win10 Forum. Originally, the February briefing was scheduled for last week, but due to various commitments and to give Insiders a chance to evaluate more 1903 builds, it was delayed. February 2019 Windows Development Briefing for 1903 Build: 18346 General: - Parallel development in progress: most Insiders are using either 1809 or 1903 builds, while several thousand are testing 20H1 builds (scheduled for next year). This is so that features requiring a long time for incubation can be tested.
- Home stretch: 1903 development is slowly coming to a close. At the moment most changes are bug fixes.
- No slow ring Insider builds: this is caused by an anti-cheat module used by games that causes green screen of death.
Windows Sandbox: - If the window is maximized, keyboard keys will be sent to the sandbox (not the host machine). This means you can now start sandboxed Narrator.
Settings: - In Update and Security/Windows Update/Advanced, branch readiness combo box is gone for all editions (Pro and higher included).
Windows Subsystem for Linux: - From Bash prompt, type “explorer.exe” to open the folder you’re working with in File Explorer.
Known issues: - Certain Creative Labs sound cards are not working properly.
- Some Realtek SD card readers are not functioning.
- In Settings/System/Storage/Storage Sense, values for combo boxes are not read by Narrator (reported, confirmed, and fix is in the works).
The next briefing will be general screen reader recommendations as reported by Insiders and screen reader vendors. Basically, you can assume that screen readers supporting Version 1809 (October 2018 Update) will work. Cheers, Joseph
|
|
Glad I didn’t stay in the slow ring. Didn’t think the anti cheating software would be a problem. I don’t play any games from the store other than the new Ear Hockey. Not sure if that accessible game has any or not.
Sent from
Mail for Windows 10
toggle quoted messageShow quoted text
From: win10@win10.groups.io <win10@win10.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Sent: Wednesday, February 27, 2019 10:54:06 AM
To: win10@win10.groups.io
Subject: [win10] February 2019 development briefing: finishing touches #WinTenDev
Hi all,
First, to new people: welcome to Win10 Forum.
Originally, the February briefing was scheduled for last week, but due to various commitments and to give Insiders a chance to evaluate more 1903 builds, it was delayed.
February 2019 Windows Development Briefing for 1903
Build: 18346
General:
- Parallel development in progress: most Insiders are using either 1809 or 1903 builds, while several thousand are testing 20H1 builds (scheduled for next year). This is so that features
requiring a long time for incubation can be tested.
- Home stretch: 1903 development is slowly coming to a close. At the moment most changes are bug fixes.
- No slow ring Insider builds: this is caused by an anti-cheat module used by games that causes green screen of death.
Windows Sandbox:
- If the window is maximized, keyboard keys will be sent to the sandbox (not the host machine). This means you can now start sandboxed Narrator.
Settings:
- In Update and Security/Windows Update/Advanced, branch readiness combo box is gone for all editions (Pro and higher included).
Windows Subsystem for Linux:
- From Bash prompt, type “explorer.exe” to open the folder you’re working with in File Explorer.
Known issues:
- Certain Creative Labs sound cards are not working properly.
- Some Realtek SD card readers are not functioning.
- In Settings/System/Storage/Storage Sense, values for combo boxes are not read by Narrator (reported, confirmed, and fix is in the works).
The next briefing will be general screen reader recommendations as reported by Insiders and screen reader vendors. Basically, you can assume that screen readers supporting Version 1809 (October 2018 Update) will work.
Cheers,
Joseph
|
|
A bit of a correction. It seems that keys are passed to the
sandbox already, even when it isn't maximized, however maximizing
the window means that hotkeys such as windows+ctrl+enter are
handled by the sandbox and not by the host.
toggle quoted messageShow quoted text
On 2/27/2019 10:54 AM, Joseph Lee
wrote:
Hi all,
First, to new people: welcome to Win10
Forum.
Originally, the February briefing was
scheduled for last week, but due to various commitments and to
give Insiders a chance to evaluate more 1903 builds, it was
delayed.
February 2019 Windows Development Briefing
for 1903
Build: 18346
General:
- Parallel
development in progress: most Insiders are using either 1809
or 1903 builds, while several thousand are testing 20H1
builds (scheduled for next year). This is so that features
requiring a long time for incubation can be tested.
- Home
stretch: 1903 development is slowly coming to a close. At
the moment most changes are bug fixes.
- No slow ring
Insider builds: this is caused by an anti-cheat module used
by games that causes green screen of death.
Windows Sandbox:
- If the
window is maximized, keyboard keys will be sent to the
sandbox (not the host machine). This means you can now start
sandboxed Narrator.
Settings:
- In Update
and Security/Windows Update/Advanced, branch readiness combo
box is gone for all editions (Pro and higher included).
Windows Subsystem for Linux:
- From Bash
prompt, type “explorer.exe” to open the folder you’re
working with in File Explorer.
Known issues:
- Certain
Creative Labs sound cards are not working properly.
- Some Realtek
SD card readers are not functioning.
- In
Settings/System/Storage/Storage Sense, values for combo
boxes are not read by Narrator (reported, confirmed, and fix
is in the works).
The next briefing will be general screen
reader recommendations as reported by Insiders and screen
reader vendors. Basically, you can assume that screen readers
supporting Version 1809 (October 2018 Update) will work.
Cheers,
Joseph
|
|
In addition, since this briefing was posted, a slow ring build
was released, though there is still an update block for people who
have the most popular games that are triggering GSODs.
toggle quoted messageShow quoted text
On 2/28/2019 3:22 AM, Mohamed via
Groups.Io wrote:
A bit of a correction. It seems that keys are passed to the
sandbox already, even when it isn't maximized, however
maximizing the window means that hotkeys such as
windows+ctrl+enter are handled by the sandbox and not by the
host.
On 2/27/2019 10:54 AM, Joseph Lee
wrote:
Hi all,
First, to new people: welcome to Win10
Forum.
Originally, the February briefing was
scheduled for last week, but due to various commitments and
to give Insiders a chance to evaluate more 1903 builds, it
was delayed.
February 2019 Windows Development
Briefing for 1903
Build: 18346
General:
- Parallel
development in progress: most Insiders are using either
1809 or 1903 builds, while several thousand are testing
20H1 builds (scheduled for next year). This is so that
features requiring a long time for incubation can be
tested.
- Home
stretch: 1903 development is slowly coming to a close. At
the moment most changes are bug fixes.
- No slow
ring Insider builds: this is caused by an anti-cheat
module used by games that causes green screen of death.
Windows Sandbox:
- If the
window is maximized, keyboard keys will be sent to the
sandbox (not the host machine). This means you can now
start sandboxed Narrator.
Settings:
- In Update
and Security/Windows Update/Advanced, branch readiness
combo box is gone for all editions (Pro and higher
included).
Windows Subsystem for Linux:
- From Bash
prompt, type “explorer.exe” to open the folder you’re
working with in File Explorer.
Known issues:
- Certain
Creative Labs sound cards are not working properly.
- Some
Realtek SD card readers are not functioning.
- In
Settings/System/Storage/Storage Sense, values for combo
boxes are not read by Narrator (reported, confirmed, and
fix is in the works).
The next briefing will be general screen
reader recommendations as reported by Insiders and screen
reader vendors. Basically, you can assume that screen
readers supporting Version 1809 (October 2018 Update) will
work.
Cheers,
Joseph
|
|