Skip to main content

Back to 2022.1

Comments

29 comments

  • Rick Sammartino Community moderator

    I have the same problem and have gone back to 2022.1 as well. Unfortunately, whatever is causing the problem in 2022.5 is being carried back to 2022.1 after reinstalling it. Spent all day yesterday trying to fix it and have to continue with it today.

    0
  • Rick Sammartino Community moderator

    Ok, so what do I do now?

    I've done a clean reinstall multiple times with 2022.1 and it keeps having the same problem as 2022.5. (Marking known good raw files as corrupt and crashing) This is the same installer that was working perfectly before last Thursdays 2022.5 update.

    I have uninstalled the program, deleted every On1 installation folder that I can find, cleaned the registry and rebooted before reinstalling. Nothing works.

    There have been no hardware changes and it's the same installer that I used previously. I have done this multiple times over the past two days. What's left?

    How can a known good installer stop working?

     

     

    0
  • Brian Lawson Community moderator

    Rick,

    It can't. I doubt the problem is with the installer. I assume you've Reset the program by now? That leaves some kind of corruption in the .on1 files as a possibility. I would find one of the "corrupt" files and try restoring its .on1 file from a backup prior to the 2022.5 update.

    0
  • Holger Danielsson

    I also think, like Brian, that the .on1 file is "corrupt". But ON1 doesn't backup these files. Only the following folders:

    - CloudConnect.db
    - Common 2022
    - ExploreService
    - Extras 2022
    - NDService

    and a file called 'ON1Sync.settings'

    So I would try the following steps:

    - backup and delete a possibly "corrupt" .on1 file
    - restore a backup of 2022.1
    - start ON1, choose the corresponding image and enter the Develop mode
    - immediately go back to Browse mode
    - as no .on1 file is present, a new one will be created with the settings of the internal database

    This may (or may not) give some further information, which may help.

     

    0
  • Brian Lawson Community moderator

    When I said to restore I should have been more specific about not using the Restore feature in the program. I meant to use your normal system backup for it.

    Thanks Holger.

    0
  • Rick Sammartino Community moderator

    Thanks for the suggestions. I think I should clarify what the problem is...

    When I first install Photo Raw It will come up and not crash because it doesn't know where my photos are yet. I've created an empty test folder and I point Photo Raw at that folder. Outside of Photo Raw I can copy any JPG into that folder and Photo Raw will work fine without crashing. However as soon as I drop any RAW file into that folder WITHOUT any sidecars, It will crash within 30 seconds and after restarting it will say that the RAW file was corrupt and will be ignored.

    I have to use the test folder because if I point Photo Raw at my Photos folder it will go into a never ending loop of crashing and marking each RAW, one at a time, after every restart.

    I initially did a number of resets to get out of the endless loop however since I stated wiping Photo Raw from the PC between installations, there is nothing to reset.

    I am not using a backup at any point during these tests. No point in restoring until i know what's going on.

    The corrupt RAW files are not corrupt. They've been checked and work everywhere else.

     

    0
  • Brian Lawson Community moderator

    Are your RAW files from a Tier 1 or Tier 2 camera? Could something in a recent Windows update have changed whatever Photo RAW is using from the OS?

    0
  • Rick Sammartino Community moderator

    They're tier 1 now. On1 added them about a year ago. So whatever is going on has to do with the raw engine.

    I thought maybe they had been removed or a new bug was making them unreadable, but that doesn't explain why the previous version won't read them any more.

    0
  • Brian Lawson Community moderator

    I'm out of ideas Rick. The way it seems to me is that either you've missed some piece of 2022.5 that is causing problems for .1 or there is something going on with your system which is causing it to react badly. Either way it's not a good thing. I'd be interested in hearing what support has to say about this.

    0
  • Rick Sammartino Community moderator

    Yea, I'm confused about this as well. If there is still some part of Photo Raw on my PC after doing a wipe, I don't know where it is. I've dug through every location that I can think of and run a registry cleaner so that should be everything.

    I'm thinking I should open the registry and run a search to verify that the cleaning actually did remove everything.

    later today I'll try installing 2021 and see what that does.

    0
  • Rick Sammartino Community moderator

    Update: Just got a message from Stevie and part of it mentions my GPU diver is out of date.

    Well now, my GPU is brand new. It's only been in the PC for 5 weeks and was installed and updated at that time. Looking at it now, it's showing a driver that's a year old!

    Ran Geforce experience and discovered that it reports a new driver, but it's failing to install it. Is it possible that it installed an older driver for some reason? I don't know what happened there, but I'm updating manually right now.

    Once it's up to date, I'll have to start my tests all over again.

    Edit: initial tests with 2022.1 show the updated driver does not fix the problem.

    0
  • David Kick

    Rick, I have heard reports of Windows updates installing older graphics drivers, that said I have never had that happen? Are you using the studio driver or the game ready drivers? I'm using the studio driver.

    In case it is a driver conflict for some reason, you could try using DDU to do a full uninstall of the Nvidia drivers and then do a clean install. Requires booting into safe mode to completely uninstall the drivers but seems to work wonders for many folks. just search for "using ddu to uninstall nvidia drivers" I'd post a link but sometimes my posts get hung up with external links.

    0
  • Rick Sammartino Community moderator

    Ah, well I did have a windows update recently, so maybe that's what happened.

    I don't know why geforce experience wasn't working earlier. I'll try reinstalling it but I can go manual if I have to. I don't think I need to go the DDU route yet, but I'll keep it in mind. I believe I'm using game ready drivers. I might try the studio driver but not right away. Too many other things to do first.

    0
  • Rick Sammartino Community moderator

    I've been checking to see how far back I have to go to find a stable version. I didn't have to go back to 2021, but only the first release of 2022 is stable.

    2022 (16.0.1.11212)  — Oct 11th, 2021     stable

    2022.1 (16.1.0.11631)  — Dec 20th, 2021   crash

    2022.1 (16.1.0.11675)  — Jan 12th, 2022   crash

    2022.5 (16.5.0.12429)  — Jun 9th, 2022    crash

    At least I have something to use while On1 figures this out.

    0
  • Martin Evans

    I have the same issue Rick and it has happened ever since 2022.1. I've tried everything I've seen recommended and nothing has helped. My graphics drivers are up to date and I have been down the DDU route.

    0
  • Rick Sammartino Community moderator

    Martin, I can send you the stable installer if you want it.

    0
  • Martin Evans

    That would be great Rick as I never had that one. I purchased at 2022.1.

    0
  • Rick Sammartino Community moderator

    Ah, well, I can upload it but can't guarantee it will run for you. Not sure how the On1 registration works. If you install it and it won't let you sign in, then you'll have to re-install the version that you have now.

    This link will be good for a week...

    this is a 1.8 gig file. Will take a while to download.

    https://we.tl/t-kvPkYJbL2g

     

     

    0
  • Martin Evans

    That you. I'll let you know how I get on.

    0
  • Martin Evans

    Thanks RIck. That one does seem to do basic things without crashing and I can even edit photos. Still flags a corrupt file (one which is ok but was was previously flagged - perhaps in database or something) but it is not labelling any more files corrupt and is not crashing within a minute of startup with me doing nothing.

    0
  • Rick Sammartino Community moderator

    Edit: While the procedure below 'might' work, I've found that it doesn't always. After the corruptfiles.log is cleared, if the files don't render, create a subfolder and simply move the files into it from OUTSIDE of Photo Raw with Explorer or equivalent to force them to be re-read. Once done, move them back where they were and delete the folder.

     

    There is a list of files that were found to be 'Corrupt' and even though you installed a different version, that list is still there and the new version is reading it. 

    Look for a file called 'CorruptFiles.log' in Roaming/On1 and either rename it or delete it. Then restart Photo Raw. Unless that list is also being kept somewhere else, I believe your corrupt files will be viewable after that.

    Note: Roaming is likely a hidden file on your C: drive under your user name.

    0
  • Martin Evans

    Deleting the corrupt files log does make the issue go away in 2022 (first release). Thank you. Now we just have to hope On1 can find a way to fix this issue and the crashing as the latest 2022 has a number of features I'd like to use but can't.

    0
  • Rick Sammartino Community moderator

    I installed todays update (2022.5.1) and it looks good. hasn't crashed yet.

    https://on1help.zendesk.com/hc/en-us/articles/4409689897613-ON1-PHOTO-RAW-2022-Release-Notes-and-Download-

    0
  • Gerry Whitmarsh

    Looking good, so far🤞

    Edit: Spoke too soon I think. There are still some problems. Edit badges don't always show and some previews, even though should be accurate, aren't. Zooming in or editing sometimes doesn't apply the edits, or applies wrong edits. Modifying something and returning to browse seems to fix it, but it is still not working correctly. Refresh preview also sometimes removes any edits (in browse). These are applied when editing though. At least the corruption seems to be fixed, so I don't (yet) need to revert to dot one.

    0
  • Martin Evans

    Sadly the latest update crashes as soon as I double click on an image in the browser to edit it. Doesn't seem to matter which image I choose, even ones never edited before. It is not saying my raw files are corrupt now but I still can't edit anything.

    I'm getting really fed up with this now. Only the very first 2022 release runs without crashing or saying my Nikon raw files are corrupt so I'm nearing a year of a paid product which I cannot access any updates.

    0
  • Martin Evans

    Spoke too soon about corrupts files. The files I try to edit and crash PR any labelled corrupt the next time you start PR.

    0
  • Gerry Whitmarsh

    I have fast preview unchecked, preview quality as accurate, but refresh preview (because the edited badge is missing) just changes the preview to the original unedited image, and still no badge. The only way to get the badge is to actually edit the image. Methinks it is time for delete settings - again and rebuild the catalogue:-(

    0
  • Rick Sammartino Community moderator

    I spoke to soon as well. 2022.5.1 sat in Browse for quite a while without crashing (which 2022.5 wouldn't do) but as soon as I started working, it started crashing again just like before.

    Back to 2022.0 again I guess.

    0
  • Martin Evans

    I don't understand why On1 can't resolve this issue. Back when I first reported it, Brian said the issue was clearly with my computer because no one else had it and yet there are obviously now loads of people seeing it. I've reported it twice to be fobbed off both times even though I sent log files, event viewer details and I even sent a crash dump analysis. I am a retired software developer of over 35 years and if we'd treated our customers like this we would have gone bust. It should be relatively straight forward to locate the issue from the crash dump analysis so I can only assume support are not passing this back to the development team to rectify. I am very frustrated as I really do want to use PR but I'm stuck with the first 2022 and missing all the improvements.

    1

Please sign in to leave a comment.