[SOLVED] WinReducer EX-100 1.8.11.0 MODEM Error 633 IN RS2 was fixed with KB4022716, but integrating the bug continue

MODEM dial up bug error 633 was created in Windows 10 RS 2.
The fix is in KB4022716 released in june. See the link
[You must be registered and logged in to see this link.]
In a clean installation Windows 10 RS 2 and using windows update the bug is fixed.
If using Winreducer for integrate the KB4022716 or the current KB4034674 the bug continue and the fix not is installed.
I has tested several Winreducer selected settings being just removed section items one for each time being features, accessories, drivers, services and others and finally creating an ISO not removing any items just integrating the KB4034674 and KB4022405 and the fix not is installed.
Windows 10 ISO is RS 2 PT-BR 64.
I will create a new ISO not selecting Windows Updates Files Cleanup in Integrate section.
Microsoft say to edit the registry to fix the issue, but even using the settings below the problem continue.
--
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan directory.
Find RequiredPrivileges key and double-click it.
Add the SeLoadDriverPrivilege at the end of the list of keys and click OK.
Append SeLoadDriverPrivilege
--
Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters directory.
Click Edit -> New -> Multi-String Value.
Name the new value as ReservedPorts.
Double-click on the ReservedPorts value and type in the 1723-1723 value.

Thanks for any help.

If installing :
- a not modified Windows 10 Pro 64 RS 2 > MODEM Error 633
- a not modified Windows 10 Pro 64 RS 2 updated using Windows Update > MODEM Error 633 fixed
- a Windows 10 Pro 64 RS 2 modified using current WinReducer with all components for Windows Update > MODEM Error 633 not is fixed even with all updates installed.
- a Windows 10 Pro 64 RS 2 modified using current WinReducer not removing services Remote Desktop (asyncmac.sys) and updated using Windows Update > MODEM Error 633 is fixed

Just adding asyncmac.sys to Windows\System32\Drivers fix the problem.
Thanks for read my post.

Hello Augusto,

Could you please confirm that the issue is solved (or not) with the newest cumulative updates (September 2017) ?

Thanks

Yes was fixed.
Thanks.