Skip to main content

Error message when starting C1 8 on Windows 10

Comments

57 comments

  • photastic
    For what it's worth, I just installed the Capture One 9 trial and that gave the same error...
    0
  • greger
    Did you find any solution to this? I just started experiencing the same thing.
    Tried reinstalling C1, didn't help.
    0
  • NNN635625480728217689
    Same problem here. I'm running the Insider preview build 14328. I have to replace my lost Sony RX100M3 and was considering another Sony, but if it's going to take months to fix this Windows 10 incompatibility, I may have to choose a different camera and software.
    0
  • SFA
    [quote="NNN635625480728217689" wrote:
    Same problem here. I'm running the Insider preview build 14328. I have to replace my lost Sony RX100M3 and was considering another Sony, but if it's going to take months to fix this Windows 10 incompatibility, I may have to choose a different camera and software.


    Is the Insider preview build now a finalised release?

    Maybe not a great idea to be running beta (? alpha?) software when making a decision about such matters.

    Why not go back to the official MS release and see how you fare with that?



    Grant
    0
  • John Doe
    I totally agree. I swear I will never understand why some people insist on using beta versions in their production environment. Beats me.

    Betas are what they are : unfinished, buggy versions, made for testing and not for using in a production environment.

    Nor will I ever understand why publishers make them available to the general public. Betas should only be supplied to developers, IMHO.

    Deciding on a different camera or RAW processor on the basis that it doesn't work with a beta version of your OS doesn't make any sense to me.
    0
  • SFA
    On another point ....

    C1 V8 has been replaced by V9 for all future developments.

    If Microsoft decide to make Windows 10 incompatible with some applications that are really not that old I think they will have some serious problems persuading bulk users - large enterprise customers for example - to make the upgrade. It took them a long time to get rid of XP.

    It is possible that some problems might be something simple like a driver that a third party will need to fix and they may do it but this one looks more like some MS compatibility issues in the MS components.


    Grant
    0
  • don maclean
    [quote="SFA" wrote:
    On another point ....

    C1 V8 has been replaced by V9 for all future developments.

    If Microsoft decide to make Windows 10 incompatible with some applications that are really not that old I think they will have some serious problems persuading bulk users - large enterprise customers for example - to make the upgrade. It took them a long time to get rid of XP.

    It is possible that some problems might be something simple like a driver that a third party will need to fix and they may do it but this one looks more like some MS compatibility issues in the MS components.

    Grant


    Just to make it really clear there are absolutely no problems with the Windows 10 current release [Version 1511 (OS Build 10586.218)] operating system.

    Suffice to say the only issues remaining are those particular to C1 8 that were there on Win 7/8/8.1 that couldn't be remedied. Those include issues with shutdown, preview building etc.
    0
  • Simon Felix
    The problem is still there with the final release version of the anniversary update (build 14393.10) which just rolled out to 350 million users.

    Support just told me that I must upgrade to C1 9 to get support. I sincerely hope that was a misunderstanding and that P1 will address this problem.

    Cheers,
    Simon
    0
  • John Doe
    According to their own support pages, it should be compatible with Windows 10 64 bit : https://www.phaseone.com/en/Search/Arti ... cleid=1701
    0
  • Simon Felix
    Yes, I pointed that out to them. I get conflicting messages. First they told me that only "Windows 10 Home" is supported, not "Windows 10 Anniversary Edition" [sic, they don't seem to understand that the Anniversary Update is available for all Windows 10 editions]. Now they tell me that it's not supported and never will be. This would leave all C1 8 users in the dark, since you cannot turn updates off in Windows 10 Home & Pro.
    0
  • Stefan Hoffmeister
    [quote="d_e" wrote:
    Support just told me that I must upgrade to C1 9 to get support. I sincerely hope that was a misunderstanding and that P1 will address this problem.


    I do hope that Phase One will fix this error message on startup of Capture One 8.3.4. Pro on Windows 10 anniversary edition:

    An unknown error occurred.

    The application was unable to gather information about the error.

    System.NullReferenceException: Object reference not set to an instance of an object at P1.C1.Program.Main()
    System.ArgumentException: Value cannot be null
    Parameter name: path1
    at System.IO.Path.Combine()
    at P1.C1.Utilities.ExceptionHandler.HandleExceptionThreadFunc

    In other words, there are two defects in the code:
    - the exception handler is buggy in triggering an null deref
    - the code item is defective in locating whatever "path1" would typically refer to

    Support case number 224687.

    I suppose everybody should submit a ticket - just copy and paste the description above.
    0
  • Simon Felix
    Support case 223269

    Now support suggested that I should disable all Windows updates. And also, that the current Windows 10 version won't be supported by C1 8 (and prior). This is getting ugly fast.
    0
  • Justin Katz
    We did not recommend disabling all Windows updates. You mentioned in your case that it is impossible to turn them off. We simply stated that you can, that is all.

    Windows 10 Anniversary Edition will not be supported with Capture One 8 and prior. It contains a .net change that breaks all Capture One versions prior to 9. This fix is already deployed so Capture One 9 customers will not be affected.
    0
  • Simon Felix
    [quote="JUK" wrote:
    We did not recommend disabling all Windows updates. You mentioned in your case that it is impossible to turn them off. We simply stated that you can, that is all.


    Please explain how to do this on Windows 10 Home. (Microsoft says, you can't.)


    Also, you recommend installing updates then. But this breaks C1 8. What now? What is the official P1 suggestion on what to do here?



    [quote="JUK" wrote:
    Windows 10 Anniversary Edition will not be supported with Capture One 8 and prior. It contains a .net change that breaks all Capture One versions prior to 9. This fix is already deployed so Capture One 9 customers will not be affected.


    There is no such thing as "Windows 10 Anniversary Edition". There is just "Windows 10". Soon, all Windows 10 users will have this update installed. There is no official way to disable updates on Window 10 Home or Pro. This means that C1 8 soon won't work anymore for all Windows 10 users.

    You stated in official documents that C1 8 supports Windows 10. As you can see here https://technet.microsoft.com/en-us/win ... -info.aspx the official (and Microsoft recommended) version is 14393.10, which I have installed. This is Windows 10, which is (according to your documentation) supported.

    Can we get a refund?
    0
  • Justin Katz
    Here ya go:





    Capture One 8 is not compatible with Anniversary edition/update, whatever you want to call it.

    Your option is to either downgrade your operating system to standard Windows 10 or upgrade your software to Capture One PRO 9.

    This is a chargeable upgrade where you can take advantage of upgrade pricing.
    0
  • Ulrick Lawrence
    Let me see if I understand PhaseOne on this issues, as a user that bought your software, I am to downgrade my OS or upgrade my software.
    So no more security updates for my system leaving my system vulnerable to malware, viruses, rootkits, key-loggers and the list goes on. Or buy an upgrade for your product, at a special upgrade price. Can you tell me why on earth would I have to pay you to fix a bug that exist is your product cause guess what older versions of Lightroom still works and if your going to force me to upgrade because your programmers left a NULL value somewhere in the code that should never have been there. For as much as I prefer C1 I would rather pay for a product that I know I'll have the use of for a few years (3-5).
    So if my only option is to upgrade then this is the first and last product from PhaseOne that I will ever buy. So Lightroom here I come!
    0
  • NN635661964762113355UL
    When I log into My Page I'm told I can't upgrade and will have to pay 279 EUR.

    Any chance of a more sensible price to keep a customer?
    0
  • Stefan Hoffmeister
    [quote="JUK" wrote:
    Capture One 8 is not compatible with Anniversary edition/update, whatever you want to call it.


    Allow me to help out with a link to the Capture One 8.3.4 release notes: http://downloads.phaseone.com/Capture%2 ... s-c3d2.pdf

    These release notes claim as Microsoft® Windows® minimum requirements: "Windows 7® SP1 64-bit, Windows 8® 64-bit, Windows 10® 64-bit"

    As it happens, I am running, this very moment, Windows 10 Home (Microsoft Windows [Version 10.0.14393]). And Capture 8.3.4 does not launch.

    Lets not beat around the bush: PhaseOne do not want to spend money on addressing an issue in Capture One 8.3.4. Logically understood, but not accepted.

    Apparently the issue is understood (Capture One 9.x has it fixed, apparently), so the fix is dirt cheap and the QA cycle should be very short.

    Alternatively, simply retarget to a .Net framework level (via manifest) which will work - https://msdn.microsoft.com/en-us/librar ... 8(v=vs.110).aspx
    0
  • Jim_DK
    [quote="NN635661964762113355UL" wrote:
    When I log into My Page I'm told I can't upgrade and will have to pay 279 EUR.

    Any chance of a more sensible price to keep a customer?


    NN635661964762113355UL,

    Your key is "for Sony" not the full blood Pro which is the upgrade you are looking at.

    Make sure you are upgrading "Pro 8 for Sony to Pro9 for Sony" to get the best price.
    https://www.phaseone.com/en/Online-Stor ... rades.aspx
    0
  • Simon Felix
    I'm glad that I'm not the only user finding this stance of P1 unacceptable. It's also notable that this is the only application I'm aware of that no longer works after this Windows 10 update.

    I will try to re-install my OS and try to block the update.


    This was probably the last time I bought anything from PhaseOne, or recommend CaptureOne. Great software, awful support.


    Jim: Your knowledge base (https://www.phaseone.com/en/Search/Arti ... cleid=1701) still states that Windows 10 64 Bit is supported. This is obviously not true. At least, please fix your documentation.
    0
  • pf234
    This is just unbelievable.

    Here's the thing.
    If Capture One 9 was really that better than Capture One 8 people would have paid for it.
    A 'stupid' HDR merging multiple exposures feature would be more than enough to make everyone want to change (which, you know, there are tons of software doing that since, like, ever...)
    Have that in mind, please. 😉

    So, right now Microsoft updated their OS, which will happen many times in the future and you are telling that you can't just make a small fix for the previous version of your software? Are you kidding?

    It really really really (and I'm really stressing REALLY) will make you look bad.

    Here's another point of view that will probabbly help you understand this situation better.
    I bought my license for Capture One 8 because your program is wonderful and it states that it is compatible with Windows 10. That means it must be, ALWAYS, compatible with Windows 10, because the 'aniversary edition' is nothing but an update. Yes, it's a big update. It's like the Service Packs in the past. But we are still running Windows 10, we bought the software because we knew we had an OS that is compatible with it and now you are saying: no, you can't keep you computer safe and updated or you'll have to pay us to fix that problem.

    I UNDERSTAND that you did not create this problem. Microsoft did. I don't know what changed and, honestly, I don't really care. All I care is your software which I bought a few months ago just broke after my system got updated. It's just silly.

    So please, understand, I really love Capture One. I've been using it a lot (not so much in last one or two months) but I have a ton of images that I have to add to the catalog and edit them and right now I just can't do it.

    Going back to the 'non aniversary' Windows 10 is not an option! It's not something that is optional. The aniversary update is a natural update that is supposed and was already installed on hundreds of millions of computers to keep them safe and ready for the future.

    So, I'm waiting for a patch for Capture One 8.3.4.
    Right now I'm going on holidays so when I come back I will need to have this working again.
    If you can't fix this then I really don't know if I can't trust a company that doesn't help their costumers when they should and I will not give you any more of my money nor promote your product (which will be really sad since you have a wonderful software).

    Think about it.
    0
  • Simon Felix
    JUK: I'm unable to apply your suggested workaround. The update does not show up in the troubleshooter tool.


    Any ideas?

    Again: Your support documents state that Windows 10 64 Bit is supported. The documents also say that these are the "Minimum System Requirements". My installation meets your criteria, yet the software does not work. Please fix it.
    0
  • Simon Felix
    The reason for the crash is the following lines in P1.C1.Program.Main()

    field = typeof (BitmapImage).Assembly.GetType("MS.Internal.MemoryPressure").GetField("_totalMemory", BindingFlags.Static | BindingFlags.NonPublic);
    if (field != (FieldInfo) null)
    field.SetValue((object) null, (object) -4611686018427387904L);


    which was probably copied straight from StackOverflow. P1 developers here try to access internal/non-public data (WHICH IS NOT PUBLIC FOR A REASON) and meddle with it. THIS IS NOT MICROSOFTS FAULT!


    The problem now is that in .NET 4.6.2 the class MS.Internal.MemoryPressure was removed (see here: leads to a 404). The P1 devs never bothered to check whether they could successfully retrieve the type itself. A single "?." instead of the "." would solve the problem. Is it really THIS hard to change a single line and redistribute the app?

    Will think about an easy workaround tomorrow.
    0
  • FirstName LastName
    I opened a ticket on both C1 account for C1 8 Pro and Microsoft community.
    What I asked microsoft is to allow Win 10 to run compatibility mode that would allow a certain .net environment.
    So I suggest search my post in Microsoft community: NullxceptionReference... win 10 anniversary update/ software/ capture one or newer: http://answers.microsoft.com/en-us/wind ... 0376733859


    For myself, c1 8 pro was functional before the 2/8/2016 anniversary update.
    I deferred upgrade for now on one machine, but over time, 10 v. 1607 will be pushed through.
    I can roll back temporarily to 1511, on the main desktop, a get back the Pro version.

    It would be helpful if PhaseOne team would intercede with Microsoft in asking to make windows
    forcing to keep previous .net environment in the system for to run compatibilty mode when associate with C1 8.

    This could be the simplest solution, also suggest push it in Microsoft community and increase the demand.


    making it your own or else. 🤭
    0
  • Simon Felix
    Here's a bugreport for the .NET framework:



    I patched C1 8 yesterday. It works now fine on my machine. It's literally a single-character code fix. But I don't think I can share my workaround, because to make it work I had to remove the licensing stuff.

    It's pathetic that PhaseOne support is unaware of how Windows 10 works, unwilling to provide proper support and fix something that is so easily fixed.
    0
  • John Doe
    If it's really that simple then my opinion is there's no reason for Phase One not to issue a fix, in order to keep their PROMISE of a Windows 10 compatibility.

    If they don't react, then maybe you should post the issue on a large-audience forum such as dpreview, to put a bit of pressure on them.
    0
  • Stefan Hoffmeister
    [quote="d_e" wrote:
    I patched C1 8 yesterday. It works now fine on my machine. It's literally a single-character code fix. But I don't think I can share my workaround, because to make it work I had to remove the licensing stuff.


    There are some frameworks out there which support code injection and runtime patching for .Net - they are all based on Mono Cecil, as far as I can tell, but allegedly operational perfectly fine on Microsoft Windows. Ihttp://reflexil.net/ might be a good starting point.

    My days for doing that kind of thing have been over for a while now, but I guess with a bit of infrastructure in place the dynamic injection part should be feasible within 10-20 hours of effort.
    0
  • Stefan Hoffmeister
    [quote="d_e"] wrote:
    field = typeof (BitmapImage).Assembly.GetType("MS.Internal.MemoryPressure")[b].GetField[/b]


    If you do daft things, at the VERY least cover your back.

    What a shame.

    I am seriously, seriously, SERIOUSLY angered by the PhaseOne refusal to fix that atrocity of their own doing. Assuming that they are professional, they'd have archived the virtual machine with the master build environment. And of course there is version control. And fully reproducible automated builds.

    No?

    Total effort required: 40 person hours _tops_, until it ends up as having been released into all distribution channels.

    Total cost (at Danish wages) - at the very most USD / EUR 8000.

    PS: I have no idea whether this would be compatible with the licensing scheme, but patching the Unicode string "MS.Internal.MemoryPressure" to a (shorter) name that in fact exists in the assembly of the BitmapImage type (PresentationCore.dll?) would get the type and simply safely(!) fail on introspection on the field retrieval. Spelunking with ILSpy / Reflector would quickly tell?
    0
  • Simon Felix
    [quote="daffy" wrote:
    PS: I have no idea whether this would be compatible with the licensing scheme, but patching the Unicode string "MS.Internal.MemoryPressure" to a (shorter) name that in fact exists in the assembly of the BitmapImage type (PresentationCore.dll?) would get the type and simply safely(!) fail on introspection on the field retrieval. Spelunking with ILSpy / Reflector would quickly tell?


    For that to work you'd have to remove the strong name signing too. If you do remove the signing, you have to remove the licensing checks.
    0
  • Edward11
    Just chiming in: I'm running into this same Fatal Error after the latest Windows 10 update. I don't have the technical knowhow to understand some of the above posts, but I wanted to thank you all for digging deeper with this issue. I'll file a support case with Phase One, and if nothing comes of it, vent on DPReview and Fred Miranda, both where I'm an active poster.
    0

Please sign in to leave a comment.