Windows10 failure to launch

[hpcdan]

I just upgraded a PC from Windows 8.1 to Windows 10.  Both BYE3 and BYE3.1.5 Premium crash in different ways.  For 3.1, I get the splash screen and the startup messages, then the main screen, then a "stopped working message"  Running in various compatibility modes does not seem to make any difference.  Any suggestions?

 

(And both versions work fine on an older Windows7 machine)

 

thanks,

Dan

[PoppaChris]

Sorry I couldn't find this thread earlier.

 

Please see my post of 12-18-2015 for comments on my test of Windows 10 with several astrophotography applications.

[hpcdan]

Sorry I couldn't find this thread earlier.

 

Please see my post of 12-18-2015 for comments on my test of Windows 10 with several astrophotography applications.

 

After I did a complete reinstall of Windows10, all was well.  There were clearly some registry entries that were incorrect in the attempt at an inplace upgrade.

[rlsarma]

Merry Christmas to all.

 

I have installed BYE 3.1.5 (Premium) on my Windows 10 (64 bit) and it is working absolutely fine. This is also working in my Windows 7 (64 bit).

 

Rajib Sarma

Digboi, Assam, India

[astroman133]

I would make sure that the .NET 3.5 Framework is active...It is accessible via Turn Windows Features On and Off link in the Programs and Features applet in the Control Panel.

[hpcdan]

Yes, checking that earlier versions of .NET were enabled was one of the first things I did.  It didn't change the error.

[astroman133]

OK, what about log file entries?  Does BYE get far enough along that it creates a log file?

 

I know that you said that you have tried different compatibility modes, but what about running as the administrator?

 

I am grasping at straws here because your issue seems to be pretty unique.

[admin]

Yes, checking that earlier versions of .NET were enabled was one of the first things I did.  It didn't change the error.

 

BYE 3.1.x requires .Net 4.0.  Make sure it is up to date.

 

Run BYE in native Windows 10 mode, no compatibility mode.

[hpcdan]

Yes, I tried all of those things -- native mode, with and without administrator privileges.  It crashes before I get a log file, dying as soon as it throws up the main screen (after the splash screen shows the license and all of the various initialization).

 

On Windows 10, both .NET Framework 3.5 and .NET Framework 4.6 are enabled.

 

As I mentioned, the earlier version of BYE3 also crashes.  It however, provides an error message:

 

Unable to cast object of type 'System.Configuration.DefaultSection' to type 'System.Configuration.AppSettingSection'

[astroman133]

Have you tried installing BYE to a different folder?

 

The "Unable to cast" error seems to indicate a problem with a corrupted BYE configuration file.  There have been reported issues with corrupted configuration files that have been solved by re-installing BYE to a different folder. This does not repair the corrupted file, but bypasses it by installing an uncorrupted copy of the file in a different folder.

[admin]

Yep, install in a different folder and you should be fine.

[hpcdan]

I removed both versions and then deleted the remaining elements in the install folders.  I think reinstalled both in new folders (distinct from the original).  In both cases, I have exactly the same errors.

 

Any other suggestions?

[admin]

Deleting the folders actually does not  do any good.  The configuration files are stored deeper in Windows.

 

Try to run with admin privileges.

 

Regards,

[hpcdan]

I tried that (running with admin privileges), both for the install and for the the app -- no change.

 

I can try looking in the registry, I suppose, for any lingering entries.

 

Any other ideas?

[astroman133]

I don't think that BYE stores settings in the Windows Registry.

 

You may want to consider downgrading your PC back to Windows 8.  It seems to me like your issue is with Windows 10.

[admin]

BYE does not store settings in the registry.

 

Please send me the log files, they may reveal something.

 

Regard,

[hpcdan]

I don't see any log file, but if you tell me where to look, I will double check.

[astroman133]

The default location is under My Pictures\BackyardTEMP\Logs

[hpcdan]

Finally, here are the XML events from Event Viewer:

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name="Application Error" />

  <EventID Qualifiers="0">1000</EventID>

  <Level>2</Level>

  <Task>100</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2015-11-25T21:31:39.000000000Z" />

  <EventRecordID>2428</EventRecordID>

  <Channel>Application</Channel>

  <Computer>ObservatoryPC.krupareed.net</Computer>

  <Security />

  </System>

- <EventData>

  <Data>BinaryRivers.BackyardEOS.Start.Camera1.exe</Data>

  <Data>3.1.5.22807</Data>

  <Data>561bf07f</Data>

  <Data>KERNELBASE.dll</Data>

  <Data>10.0.10240.16384</Data>

  <Data>559f3b2a</Data>

  <Data>e0434352</Data>

  <Data>000b3e28</Data>

  <Data>1608</Data>

  <Data>01d127c89d4d2e0e</Data>

  <Data>C:\Program Files (x86)\BackyardEOSv3.1 Try\BinaryRivers.BackyardEOS.Start.Camera1.exe</Data>

  <Data>C:\WINDOWS\SYSTEM32\KERNELBASE.dll</Data>

  <Data>a6552290-6ede-4f33-8902-a45baa70bb47</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

----

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

  <Provider Name=".NET Runtime" />

  <EventID Qualifiers="0">1026</EventID>

  <Level>2</Level>

  <Task>0</Task>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2015-11-25T21:31:39.000000000Z" />

  <EventRecordID>2427</EventRecordID>

  <Channel>Application</Channel>

  <Computer>ObservatoryPC.krupareed.net</Computer>

  <Security />

  </System>

- <EventData>

  <Data>Application: BinaryRivers.BackyardEOS.Start.Camera1.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.TypeInitializationException Stack: at System.ServiceModel.Diagnostics.TraceUtility.SetEtwProviderId() at System.ServiceModel.ChannelFactory..ctor() at System.ServiceModel.ChannelFactory`1[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(System.Type) at System.ServiceModel.ChannelFactory`1[[system.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]..ctor(System.ServiceModel.Channels.Binding, System.ServiceModel.EndpointAddress) at OTelescope.BackgroundWorker.Shared.BackgroundWorkerClientContext.StartServer(Boolean) at OTelescope.BackgroundWorker.Shared.BackgroundWorkerClientContext.<Initialize>b__6(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()</Data>

  </EventData>

  </Event>

[hpcdan]

The default location is under My Pictures\BackyardTEMP\Logs

 

There's nothing there.  But, here is the Windows Error Report (WER):

 

Version=1

EventType=CLR20r3

EventTime=130929657097821359

ReportType=2

Consent=1

UploadTime=130929657100477746

ReportIdentifier=937cf7e4-93c7-11e5-82b7-a088698c4055

IntegratorReportIdentifier=4cf66eb7-1d93-4e4f-850e-4ce5f73296a4

WOW64=1

NsAppName=BinaryRivers.BackyardEOS.Start.Camera1.exe

Response.BucketId=eeacfc47da2188f18771e7243742fee0

Response.BucketTable=5

Response.LegacyBucketId=128961768695

Response.type=4

Sig[0].Name=Problem Signature 01

Sig[0].Value=M301ANEATRGLQEL5YQ3MI3IDJE3X3Q0D

Sig[1].Name=Problem Signature 02

Sig[1].Value=3.1.5.22807

Sig[2].Name=Problem Signature 03

Sig[2].Value=561bf07f

Sig[3].Name=Problem Signature 04

Sig[3].Value=System.Configuration

Sig[4].Name=Problem Signature 05

Sig[4].Value=4.6.79.0

Sig[5].Name=Problem Signature 06

Sig[5].Value=556bc656

Sig[6].Name=Problem Signature 07

Sig[6].Value=262

Sig[7].Name=Problem Signature 08

Sig[7].Value=28

Sig[8].Name=Problem Signature 09

Sig[8].Value=System.TypeInitialization

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=10.0.10240.2.0.0.768.101

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=bdcb

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=689d

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=689d12abf00dd47c453b5e1a156c0fa3

UI[2]=C:\Program Files (x86)\BackyardEOSv3.1 Try\BinaryRivers.BackyardEOS.Start.Camera1.exe

UI[3]=BinaryRivers.BackyardEOS.Start has stopped working

UI[4]=Windows can check online for a solution to the problem.

UI[5]=Check online for a solution and close the program

UI[6]=Check online for a solution later and close the program

UI[7]=Close the program

LoadedModule[0]=C:\Program Files (x86)\BackyardEOSv3.1 Try\BinaryRivers.BackyardEOS.Start.Camera1.exe

LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll

LoadedModule[2]=C:\WINDOWS\SYSTEM32\MSCOREE.DLL

LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNEL32.dll

LoadedModule[4]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll

LoadedModule[5]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll

LoadedModule[6]=C:\WINDOWS\SYSTEM32\msvcrt.dll

LoadedModule[7]=C:\WINDOWS\SYSTEM32\sechost.dll

LoadedModule[8]=C:\WINDOWS\SYSTEM32\RPCRT4.dll

LoadedModule[9]=C:\WINDOWS\SYSTEM32\SspiCli.dll

LoadedModule[10]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll

LoadedModule[11]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll

LoadedModule[12]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll

LoadedModule[13]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll

LoadedModule[14]=C:\WINDOWS\SYSTEM32\combase.dll

LoadedModule[15]=C:\WINDOWS\SYSTEM32\GDI32.dll

LoadedModule[16]=C:\WINDOWS\SYSTEM32\USER32.dll

LoadedModule[17]=C:\WINDOWS\SYSTEM32\IMM32.DLL

LoadedModule[18]=C:\WINDOWS\SYSTEM32\MSCTF.dll

LoadedModule[19]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll

LoadedModule[20]=C:\WINDOWS\SYSTEM32\VERSION.dll

LoadedModule[21]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

LoadedModule[22]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll

LoadedModule[23]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\68b0897c4cade2a6a72889bff2bd0904\mscorlib.ni.dll

LoadedModule[24]=C:\WINDOWS\SYSTEM32\ole32.dll

LoadedModule[25]=C:\WINDOWS\system32\uxtheme.dll

LoadedModule[26]=C:\Program Files (x86)\TeamViewer\tv_w32.dll

LoadedModule[27]=C:\WINDOWS\SYSTEM32\SHELL32.dll

LoadedModule[28]=C:\WINDOWS\SYSTEM32\windows.storage.dll

LoadedModule[29]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10240.16384_none_49c02355cf03478c\COMCTL32.dll

LoadedModule[30]=C:\WINDOWS\SYSTEM32\shcore.dll

LoadedModule[31]=C:\WINDOWS\SYSTEM32\powrprof.dll

LoadedModule[32]=C:\WINDOWS\SYSTEM32\profapi.dll

LoadedModule[33]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll

LoadedModule[34]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll

LoadedModule[35]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\33c22596ef36ae634d7c7fa0d834a1a3\System.ni.dll

LoadedModule[36]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\fbdef51c0e89515e75a83e4751c79d4a\System.Drawing.ni.dll

LoadedModule[37]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\6d1d2ffff0311fe12f1d5c3d250ce510\System.Windows.Forms.ni.dll

LoadedModule[38]=C:\WINDOWS\SYSTEM32\cryptsp.dll

LoadedModule[39]=C:\WINDOWS\SYSTEM32\bcrypt.dll

LoadedModule[40]=C:\WINDOWS\system32\rsaenh.dll

LoadedModule[41]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Ente96d83b35#\917396a2d0ba40ff95871ca20425a67a\System.EnterpriseServices.ni.dll

LoadedModule[42]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\b985aa78aab4528aaa723b90b52986d1\System.Core.ni.dll

LoadedModule[43]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\8cc5a2101f88ecce594d053af3256a7e\System.Configuration.ni.dll

LoadedModule[44]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\a73b5a097f4a7e26470de5940f71e623\System.Xml.ni.dll

LoadedModule[45]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll

LoadedModule[46]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Accessibility\f59f950b523dff2444c37908821ac499\Accessibility.ni.dll

LoadedModule[47]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Microsoft.V9921e851#\2ffde07819386a73040e2ac5856daa53\Microsoft.VisualBasic.ni.dll

LoadedModule[48]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Data\70135570ca135349ed66dc855f868945\System.Data.ni.dll

LoadedModule[49]=C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll

LoadedModule[50]=C:\WINDOWS\SYSTEM32\WS2_32.dll

LoadedModule[51]=C:\WINDOWS\SYSTEM32\NSI.dll

LoadedModule[52]=C:\WINDOWS\SYSTEM32\CRYPT32.dll

LoadedModule[53]=C:\WINDOWS\SYSTEM32\MSASN1.dll

LoadedModule[54]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Transactions\625bd1acaf45990a194af5deefa57e55\System.Transactions.ni.dll

LoadedModule[55]=C:\WINDOWS\Microsoft.Net\assembly\GAC_32\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll

LoadedModule[56]=C:\WINDOWS\SYSTEM32\urlmon.dll

LoadedModule[57]=C:\WINDOWS\SYSTEM32\iertutil.dll

LoadedModule[58]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Management\82ba8dbdb3f502dbe3513694531ba77e\System.Management.ni.dll

LoadedModule[59]=C:\WINDOWS\SYSTEM32\clbcatq.dll

LoadedModule[60]=C:\WINDOWS\system32\wbem\wmiutils.dll

LoadedModule[61]=C:\WINDOWS\SYSTEM32\wbemcomn.dll

LoadedModule[62]=C:\WINDOWS\system32\wbem\wbemprox.dll

LoadedModule[63]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\wminet_utils.dll

LoadedModule[64]=C:\WINDOWS\system32\wbem\wbemsvc.dll

LoadedModule[65]=C:\WINDOWS\system32\wbem\fastprox.dll

LoadedModule[66]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10240.16384_none_d15682eeaf714889\gdiplus.dll

LoadedModule[67]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll

LoadedModule[68]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10240.16384_none_3bccb1ff6bcd1849\comctl32.dll

LoadedModule[69]=C:\WINDOWS\system32\dwmapi.dll

LoadedModule[70]=C:\WINDOWS\SYSTEM32\DWrite.dll

LoadedModule[71]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\0ae5397e59e320e24681e9297b413ed2\System.Runtime.Serialization.ni.dll

LoadedModule[72]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\dc92ba4ca16df1772d16803348f5fff5\SMDiagnostics.ni.dll

LoadedModule[73]=C:\WINDOWS\SYSTEM32\PROPSYS.dll

LoadedModule[74]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll

LoadedModule[75]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Microsoft.CSharp\b4e5b29c9abf8f1f7ce85d6c68c26de7\Microsoft.CSharp.ni.dll

LoadedModule[76]=C:\WINDOWS\system32\dataexchange.dll

LoadedModule[77]=C:\WINDOWS\system32\dcomp.dll

LoadedModule[78]=C:\WINDOWS\system32\d3d11.dll

LoadedModule[79]=C:\WINDOWS\system32\d2d1.dll

LoadedModule[80]=C:\WINDOWS\system32\dxgi.dll

LoadedModule[81]=C:\WINDOWS\system32\twinapi.appcore.dll

LoadedModule[82]=C:\WINDOWS\system32\USERENV.dll

LoadedModule[83]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\2323d28fd5a3da6b8015c47a7b1bd076\System.ServiceModel.Internals.ni.dll

State[0].Key=Transport.DoneStage1

State[0].Value=1

FriendlyEventName=Stopped working

ConsentKey=CLR20r3

AppName=BinaryRivers.BackyardEOS.Start

AppPath=C:\Program Files (x86)\BackyardEOSv3.1 Try\BinaryRivers.BackyardEOS.Start.Camera1.exe

NsPartner=windows

NsGroup=windows8

ApplicationIdentity=EB9A8DDA04DB328FE1C1BB04491BA64E

[admin]

I know you said .net was installed but this looks like a classic .net install gone bad.  Please re-download .net framework 4.0 and reinstall/repair.

 

If the log files are not created the issue is before BYE even starts.  The 1 line of code is to create the logfile... and if that fails the issue is usually .net not running properly.

 

Keep us posted, this is a strange issue.

 

What anti-virus are you using?

 

Regards.

[hpcdan]

I know you said .net was installed but this looks like a classic .net install gone bad.  Please re-download .net framework 4.0 and reinstall/repair.

 

If the log files are not created the issue is before BYE even starts.  The 1 line of code is to create the logfile... and if that fails the issue is usually .net not running properly.

 

Keep us posted, this is a strange issue.

 

What anti-virus are you using?

 

Regards.

This is Windows 10 -- it doesn't let you install the .NET 4.0 framework from a download.  (I know, I tried.  The installer warns you that .NET 4 is already installed and exits.  Nor can you uninstall it from the control panel)

 

 I've been suspecting .NET from the beginning, because I have issues with a few (just a few) other programs as well.  However, as I noted above, it is not obvious how to install the appropriate version of .NET on Windows 10.  If anyone knows, please share with me.

 

Windows 10 comes with builtin antivirus -- Windows Defender.  I have already tried disabling it -- no joy.

[astroman133]

Do you have the Canon EOS Utility installed?  Does it start up and connect with the camera? My guess is that the EOS Utility will work.

 

I have not heard of any other reports of your error before and there are quite a few people who have upgraded to Windows 10 and run BYE. It seems like it could be a problem with the .NET CLR or one of the other components of Windows 10.  That is why I suggested rolling back to Windows 8.1.

 

I am going to withdraw from the discussion since I don't have any more suggestions to offer.

[admin]

That would be an interesting test.  EOS Utility is also built using .net.  Thought I think they use .net 4.5.  I'm not 100% sure though.

 

Regards,