Alert: ASCOM broken by windows update!


#81

We should count to 10 before celebrating. There is scope for a big muddle here, with loads of combinations. We have Win10&Win 8 in 64-bit or 32-bit and that coupled with whatever update one installed, uninstalled, DCOM’d etc.


#82

I like this- I can block further updates by sticking a whopping image file on my Stick !


#83

Hi Buzz you are spot on. I looked through my updates and didn’t have one that was said to cause these problems. KB4056898 was quoted as the cause, this has never been downloaded to my laptop although I had one issued at a similar time KB4056895 which may have caused the issues on mt particular set up. My laptop runs windows 8.1 x64, so the update I quoted relates to 8.1 64 bit machines.

As you say could be a muddle

Regards

Alec


#84

I have finally just said screw all this nonsense and did a $80 mostly permanent fix. Since I have a separate PC in my observatory and control that with Radmin via a dedicated Ethernet cable, I simply bought a second router and second NIC card, set up a separate local subnet and did not connect that router to the internet.

Since the patch was never applied to that PC now it never will be and since that PC can no longer connect to the the internet, it is close to risk free.

MS can’t update what it can’t get to. The only time I will update it in future is if something I need stops working.


#85

Just a note for those with SB mounts. SB just released a new daily build that supposedly will fix the windows communications issues with SB mounts and TSX.

Anyone brave enough to try this with the windows update, let us know if it works!

From the download site for this daily build:

"Hopefully a fix to the ‘Windows 10 V1709 Update’ that prevented external programs from being able to use TheSky’s scriptable, COM objects.


#86

What about SGPro and other software updates?


#87

SGPro itself has no issues the Windows update.


#88

I have an Intel Stick with Win10x64 pro on. It is not my main imaging computer but one I use for portable use. I have not bothered trying to apply workarounds to it and it has all MS updates and now, the latest TSX daily build. When the weather clears, I’ll connect it to my MX in the observatory and see if PHD 2 guides with Direct Guide. I’ll drop you a line.


#89

Thanks! Yes, the weather here has been awful as usual in the winter,
nothing but clouds in the forecast. I also have a brand new Moravian
16200 that has seen nothing but bench testing because of the weather.
The New Mexico site has decent weather but their service guy screwed up
our Paramount ME down there so we are waiting for a SB guy to come and
fix it. It still works but is far from optimal.

buzz wrote:


#90

Just a quick note regarding ATIK equipment.

I posted this sometime back…

Good news is the ‘new’ drivers from ATIK fixed the issue with no real jumping through hoops.


#91

That’s great, how new are the new drivers? I assume they’re on the Atik website


#92

That particular udate was dated Dec1 of 2017. I don’t know if there are additional updates since but it was a pretty substantial change to the previous. Most noteably the change of the name for the filter wheel driver.


#93

I did try this in daylight- using the manual guide tool in PHD2 and watching the telescope position in TSX(version 11355). With 1000ms moves, if I selected DirectDrive in the TSX ASCOM driver, the mount did not respond. If I selected PulseGuide in the ASCOM driver, the mount moved as expected. Switched back and forth, disconnected, reconnected, no difference.
So, as far as I can tell, at the moment, this new TSX daily build does not allow me to use SGP with DirectGuide in Win10. As far as I can tell - both guide methods use the CCDSoftCamera API. I remember I have a script from Chris for moving the mount with DirectGuide. I will try that too but expect a similar result.


#94

I know that MS released an out of band update this weekend to back off some aspects of the problematic update. Does anyone have this new update installed and, if so, has it (plus the SB update) fixed the Directguide issue?


#95

My Intel Stick has OS build 16299.192 (Jan 3) - which is the latest for the 64 bit and reports it is completely up to date. I cannot get it to work with DirectGuide with the SB update.


#96

Did you try Bob Denny’s work around at:

http://forums.dc3.com/showthread.php?11182-ALERT-Windows-10-Update-KB4056892-Reported-Problems&p=67734#post67734

Peter


#97

Peter- no, I explicitly did not try any workarounds (please see my prior post). I wanted to evaluate what a standard customer would see. As far as I can tell the SB daily build should have fixed the COM issues, but in my case, that does not appear to be the case. It is important that the various programs sort themselves out without resorting to work-arounds.


#98

That works for some, but not all, problems created by the MS update. Specifically, it does not help for the TSX issues.


#99

Daily build 11360 had just been released today (29th) and Daniel asked me to confirm if this works. It won’t be until tomorrow now.

Just discovered Daily Build 11355 breaks DirectGuide with SGP/PHD2 in Win7 x64 too! One step backwards…
Daily Build 11360 does restore DirectGuide to Win 7 X64. Will try Win10 x64 tomorrow night.


#100

Just tried that version Chris, had to back it out, running Win 10 WITHOUT the MS update installed currently so will interested your results.


www.mainsequencesoftware.com