Luminous Landscape Forum
Raw & Post Processing, Printing => Capture One Q&A => Topic started by: Malcolm Payne on January 18, 2023, 04:42:34 am
-
Fresh installation of C1 23 on a new build high-spec Windows 11 machine.
Opening C1 generates a .NET unhandled exception error: ‘The system cannot find the file specified (0x80070002)’.
I have a support ticket open with C1, who advise that “… for some Windows setups, Capture One needs a different .NET installation. For that reason, we recommend getting the latest .NET 6.”
I have installed .NET 6, and also tried reinstalling C1, but the issue remains. I haven’t yet heard back again from C1 after further updating them.
Installing the latest 16.02 release over the top has made no difference, and I couldn't find anything obvious in Event Viewer.
Has anyone else seen this or similar, or has any suggestions that might help? There is nothing unusual about the new machine build (i9-13900 on an Asus z790 board), which is running at stock speeds and thus far hasn’t shown any issues with other software. It’s intended as a replacement for my previous main production PC, so it’s essential that I get everything up and running ASAP.
Thanks in advance for any thoughts or other confirmation on the same issue.
-
Update: I have now narrowed this issue down to the Resource Hub, which starts up automatically the first time following a new installation of C1 but in this instance appeared as a completely blank window accompanied by the aforementioned .NET error. By unticking 'Show on Startup' I can now open C1 as usual.
The issue is completely reproducible by opening Resource Hub from the C1 Help menu, whereupon the same blank window and error message reappears, so I'm guessing it's connected with whatever process controls the rendering in that window.
So, a workaround rather than a fix so far, but at least C1 should now be usable providing the issue doesn't affect anything elsewhere in the program.
If anyone does experience anything similar, please do raise a support ticket with C1, as the more reports they receive, the greater the chance of a prompt fix.
-
Glad you have a work around. I don't have a problem with the Resource Hub dialog. I didn't know you can turn it off. I'll head over there and do that now since it really isn't that useful.
-
Curiouser and curiouser ...
Last week Capture One support asked me to add a new admin account and install and run C1 from there to try and narrow things down further. Which I did, with precisely the same error on that account.
This morning I had a further email requesting the C1 logs from the new account.
Prior to switching accounts to the new one, I first tried opening C1 again from my original account, and it showed the identical original error.
I then changed to the new account and tried opening C1 again from there before saving the logs, and this time it opened normally from that account.
Even more puzzling, after reverting back to my original main account C1 opened correctly in that account on the first attempt and now continues to do so every time without error. Just to be sure, I rebooted the computer and C1 continues to start up as normal on the main account.
I had made no changes to the system during the course of the above, which was all one continuous process with no interruptions or deviation. Nor, according to the Windows update history, had there been any recent background system updates apart from a MS Defender security update at some unspecified time this morning.
I am completely at a loss to explain the change in behaviour, unless the previous MS Defender security definitions had perhaps silently blocked an essential file which had then been unblocked in this morning's update, but that's possibly clutching at straws. Unfortunately the update history doesn't give an exact time for the update; the nearest I can get to that is that it states the system as being up to date at 10.23 a.m., which does roughly coincide with the times when I was working through the above, but I can't be sure where I was in the process at that time.
I've asked Capture One if they can perhaps shed any further light, otherwise I'll just have to put it down to one of those weird computer glitches that seem to happen from time to time.
-
Mysteries kinda suck. On the other hand glad you are up and running. May things stay that way for you.