Windows 10: Dial-up error 633 w/build 15063 Pro

Dial up worked fine in 1607. With the update to Creators' build it now reports "error 633 - com port in use."

The modem has always been on COM 3. Tried ports 5, 9, 11. Same. COM 1, the only port listed in Device Manager, is shown as "in use." Process Explorer shows no info when queried for "serial."

Searched, read and tested virtually every suggested fix...

Uninstalled and reinstalled dial-up connection
Uninstalled modem (in Safe Mode), booted normally and updated modem driver
Created a "reservedport" registry entry for port 1723
Ran netstat -aon search for port 1723; it's not listed
Disabled the broadband adapter temporarily and turned off the broadband modem temporarily

SFC /scannow shows no errors.
There are no VPN connections on this PC.
This isn't a modem fault; MS FAX works fine.

There was no DUN failure when 1511 O/S was updated to 1607. Yet, some months later, the 633 error appeared. An earlier 1607 image was restored and DUN was again functional.

Applied Creators' update to that earlier 1607 restore and over a 1511 restore. DUN had been functional on them all until this update broke it. Have others had the same experience? Is there a fix?

:)

 

dongle connectivity

Hi Mohd,

We are aware of an issue with modem connectivity and are working on releasing a solution in a future update. To help you resolve this concern, there is a work around given by Jestoni Mac on this link:

Dial-up error 633 w/build 15063 (1703 Creators) Pro. It was found helpful by 21 people and we hope you'll be one of them.

Let us know if you have further concerns.

 

win 10 2017 The Creators Update problem

There´s a temporary solution in this thread:

Dial-up error 633 w/build 15063 (1703 Creators) Pro

 

Seeing exact same issue here in Canada with Alcatel USB data stick (error 633). All was fine until the CU (Creators Update). One has to think we got an issue here. If anyone finds a solution (other than a revert to previous build), I hope they post it.

 

This may indeed be an issue. Here is a response posted by a moderator of an MS Technet forum...

"Hi, Thanks for your discovery and studying.

I searched online and find out some others also meet with same issue, the error 633 just appears after upgrade to 1703 version.

I have submitted your discovery and this case to Microsoft product team via our internal feedback tool, let’s wait for update to fix this issue or deliver a workaround. For current situation, in order to continue working, please roll back to 1607 version."

Further, an MS 'answer desk' agent opined that build 15063 (1703) may be superseded by another that corrects the fault. A phone session is scheduled with higher level support shortly and the gist will be reported here.

As DUN and FAX are not priorities, be skeptical. An MS FAX failure persisted throughout the Win 8/8.1 cycle despite it being widely reported. The fix (a DLL) was posted to their own forums, yet the fault wasn't corrected until Win 10.

 

Yes, rolled back, working again. Though it's actually a friends laptop, I felt bad for "helping him upgrade" & the worse is that it is "Home" edition so it can not be set to defer the upgrade, so it just may upgrade and break again.

 

MS Level II support made the following suggestions on 4/8/17 and promised that the issue would be kicked up the chain...
1. Contact ISP for latest driver
2. Visit network adapter manufacturer WEB site for latest driver
3. Wait a few weeks for a new build and/or patch

A 4/12/17 phone discussion with MS pegs this as a manufacturer's driver issue, not under Microsoft's control. Precisely whose or which driver is unknown.

 

If what the MS tech stated to me was valid, that is the case. However, he said that the auto-update process either was not in effect - or could be overridden - in version 1511. So that may be the answer for your friend.

 

Hello! guys,I have had the same problem after i am updating to Creators Update , and I have already done all the steps that Borgus advised successfully , but problem not fixed! ,What next step are you recommending me ?!

 

This is a fault in Windows 10 version 1703 (Creators). See this thread... Dial-up error 633 w Pro - Microsoft Community