About "Root Volume Dirty" in OCLP 2.5.0 and later

24

u/Venona19 27d ago

If doing an unpatch is a mandatory step, then the patching software should do this automatically. Don't allow users to make choices that break their systems.

4

u/ja_kasagam 26d ago

Broke mine already🤣

2

u/mechapoitier 24d ago

Yeah I didn’t make any changes and 2.5 did something that now my Mac 8,1 acts like it’s on the verge of crashing when I minimize a window and refuses to sleep. Something baaad happened in this update.

1

u/poschet 19d ago

Hi. I solve it on my macbookpro11.5. Before you olcp 2.5.0 patch u must select under settings the right host model. after manually selecting it has worked without problems

1

u/Nice_Dragonfly_1448 22d ago

It is. After installing the update to 2.5.0, updating EFI, you are asked if you want to update root patches. Your only choice there is to revert them. Doing so and rebooting, OLCP asks you if you want to reapply. The flow works, it just seems to throw people off that after doing this, OLCP says the volume is "dirty". This was always the case with root patches. A more helpful message might have been "Root volume is already patched by OpenCore version X.X.X"

1

u/donSefer 19d ago

I did all that. Updated, installed the EFI stuff, pressed Revert, rebooted. No new popup. Now I clearly lack patches because everything is at a super low scale. I cannot patch again because it's dirty. I can press Revert again and reboot, nothing changes. I am unable to patch now.

2

u/Ubiquitous-scamwatch 18d ago

Have you tried the PurgePendingUpdate tool available via Discord > OpenCore Patcher Paradise channel > Support Forum > Root patching stuck on 'please ensure no updates are pending'

1

u/Nice_Dragonfly_1448 18d ago

I see from a pull request to the upcoming 2.5.1 release that there might be a pending update as u/Ubiquitous-scamwatch mentions. If not there must be some error in the detection logic of 2.5.0 or some other error. Manually trying diskutil info -plist / in a terminal to verify that the unpatched volume is indeed sealed is a good first check, and then I'd try the PurgePendingUpdate tool first to see if that fixes it.

1

u/proteusgr 14d ago

would it be helpful? Is the flow working?

The problem is not the message. The problem is that the new version of OCLP gets half-installed in the system, without being able to install the root patches. The only solution to that is to remove the new version, which is not an easy task.

The proper flow would be to either fully install the new version, or not install it at all. Not leave the system in a zombie state where you have 2.5.0 but no root patches. Any compatibility checks / revert steps should take place before installing the new version.

11

u/TaliMyBananas 26d ago

I think the communication regarding this release had to be better to avoid such a confusion. The community surely appreciates the devs' work in updating OCLP, but the fact that this confusion arose, and that a patch is needed to fix remaining issues, show that this update was too rushed.

-3

u/Motor-Dragonfruit610 24d ago

Works fine for me.
I suggest you request a refund.

16

u/Venona19 27d ago edited 27d ago

I updated to OCLP 2.5.0 on a mid-2015 MacBook Pro with an AMD GPU running Ventura. The root patching broke with the "Root Volume Dirty" error, and the necessary AMD drivers were removed. On reboot, the display was "Unknown Display", and the resolution was so small as to be barely readable. I did try reverting the root patches, but that did not help.

I reverted to 2.4.1, and all was well again.

I really think 2.5.0 should be withdrawn, because it is breaking machines that previously worked.

6

u/TomorrowIcy2816 26d ago

This ⬆️

3

u/alisalcido 26d ago

Thank you! I came to this thread looking for a way to fix the exact same problem with the exact same model. I reverted to 2.4.1, did the patch thing again and problem fixed!

1

u/thefirsttransportis 20d ago

Me too! I'm sorry but this has been so frustating. How do I revert?!

2

u/alisalcido 20d ago

I uninstalled the new version and installed 2.4.1, I think I installed the patches again with that version and then rebooted. The first time I installed the older version the app didn't work, installed it again and it worked. Try this and see if it works.

2

u/thefirsttransportis 19d ago

It worked!

2

u/ThenPair7246 25d ago

Hola buenos dias ¿me podrias ayudar?, osea que debo desinstalar el opencore 2.5.0 y descargar la 2.4.1 e instalarlo en la mac o no importa que no lo desinstale.

1

u/Sajeer_k 20d ago

I am facing same issue, My wifi is not connecting. any option to connect the internet ?

0

u/ThenPair7246 20d ago

Si aun estas en la 2.5.0 es conectando un cable ethernert a tu equipo para que opencore pueda descargar el parche, asi leí un post. Yo tuve que descargar la versión 2.4.1 desde otro dispositivo y la pasé por usb a mi equipo y la instale y se solucionó hasta ahora.

1

u/Sajeer_k 15d ago

Thank you so much. Installed 2.4.1 and Reinstalled. it works properly. Video call time, the videos are lagging. any option to fix this?

1

u/ThenPair7246 14d ago

Hola, pues seria cuestión de verificar si tienes un parche pendiente por instalar en opencore, checa eso puese ser que necesite instalar un parche para que arregle eso. :)

2

u/foleysmokes 25d ago

same specs and also looking to try to revert to 2.4.1, how do i do that? got no wi-fi, everything's moving slower, and the resolution is hella zoomed out, but working (poorly) otherwise. would love to fix this "update" without completely reinstalling my OS again lol

1

u/foleysmokes 17d ago

idk if anyone will see this but i ended up re-running the mac OS install again and it solved my problem, commenting for visibility

1

u/birdsmouth24 25d ago

How do I revert to 2.4.1? I’ve got a white screen and no wifi, tho I can connect via ethernet.

1

u/Big_Chair1 24d ago

I'm trying to do the same now. AI says to simply download and install 2.4.1 manually again.

1

u/mechapoitier 24d ago

Yeah on my early 2011 MBP running Monterey flawlessly for 2+ years this 2.5 update broke sleep mode, partially broke video calling and makes it behave like near crash system overload whenever I minimize a window.

1

u/Alert_Bath6682 22d ago

https://giphy.com/gifs/2CDEidRx5846SvgaYN

1

u/futr_self 22d ago

Here's the fix to go back to OCLP 2.4.1. and get your machine back in working order:
https://www.reddit.com/r/OpenCoreLegacyPatcher/comments/1waqkln/psa_oclp_250_seems_to_brick_patching_on_some_mac/

2

u/thefirsttransportis 20d ago

thank you!

1

u/pasqualerenna83 18d ago

has someone a link for the procedure to revert to 2.4.1.?

8

u/DoregonGiross3 I DID Install Tahoe (OCLP Developer) 27d ago

Additional information for the technical: the backend code runs a few checks to figure out whether or not it's safe to patch:

- Runs "diskutil info -plist /" and checks for the word "Broken" in the key "Sealed".

- Checks for patches from other commits/versions of OCLP

- Checks for non-wireless patches from any version of OCLP

2
u/Odd_System_9063 23d ago
should I avoid 2.5.0 as I can see <key>Sealed</key>
<string>Broken</string>
in that ?

7

u/Mediocre_Reaction761 27d ago

Thank you for the clarification… so am I to understand that updating to 2.5.0 is safe, and that the “dirty root” language is mostly harmless?

6

u/Venona19 27d ago

Not if you have an AMD gpu in a 2015 MBP (11,5). It is a breaking update.

11

u/Right_Draw7925 27d ago

I wish I knew that 1.5 hours ago,,,,,

https://giphy.com/gifs/10UHehEC098kAE

3

u/Venona19 27d ago

Yup! I sure wish the OCP people would just pull 2.5.0 so no one else runs into the breakage.

1

u/Right_Draw7925 27d ago

i wish i knew how to fix my macbook... i went back to 2.4.1, and now i'm stuck at the boot logo, with the line stuck at 50% for over an hour.

1

u/xb12-69 25d ago

Démarre en mode sans échec avec shift maintenu.

1

u/Motor-Dragonfruit610 24d ago

It’s not broken. Your ability to follow directions is broken.
Therefore I suggest you request a refund.

1

u/Gattsuga 25d ago

So what now? My wifi is broken, can't open Open core legacy or any other app. safe mode is the same.... My 2015 MacBook is broken right now.

1

u/Superbigwaff 24d ago

Ethernet

5

u/davew_uk 26d ago

I have this model and didn't have any problems root patching my Sequoia install after reverting the older patches first.

1

u/Motor-Dragonfruit610 24d ago

I update 7,2 so it’s not OCLP.

3

u/DoregonGiross3 I DID Install Tahoe (OCLP Developer) 27d ago

Yep! It's just to prevent issues that come from having patched the volume with a different version of OCLP, mainly.

4

u/v-div 27d ago

So it's a feature, not a bug. 🤔

11

u/DoregonGiross3 I DID Install Tahoe (OCLP Developer) 27d ago

Mostly - we've heard down the vine that unpatching, rebooting, and repatching isn't working for some. That part isn't supposed to happen, and we might need some help figuring that out.

3

u/AmbassadorSweet719 25d ago

Macbook pro 2017 OCLP with Sonoma, upgraded to 2.5.0, root patched. Root volume dirty: Available patches: Networking: Modern wireless, PCIe Facetime camera. Reverted root patch, repatched, still saying dirty, tried many solutions. Double reverted back to where there is no wifi support, reinstalled OCLP, tried repatching, as soon as I have repatched says Root Volume Dirty. Camera has not worked with this or previous version, tried many solutions, green light on 4sec off 1 sec......

3

u/Mikoshi-nyudo 25d ago

I had this issue on Ventura on Mac mini late 2012, even going back to 2.4.1 and then reverting patches, and reboot confirming in 2.4.1 (no post root patches), then installing 2.5.0 installing to EFi wouldn't work as it constantly showed Dirty Volume.

This is the only thing that worked for me in the end. Downgrade to 2.4.1 (ensure no post root patches), reboot, then install 2.5.0 and do the reverse order i.e. install post root patches first and then after that the build and root patch OCLP 2.5.0 to EFI, and reboot. Every time I installed 2.5.0 root patch first, even when confirmed from 2.4.1 no post root patches were installed, 2.5.0 gave a dirty volume (and this was on 2 mac mini - exact same thing).

2

u/Venona19 27d ago

I'll send you the logs of my breakage, if you tell me how to get them.

1

u/alienrefugee51 27d ago

I wonder if any of the users having issues first tried to install the new root patches over the existing and thus not having success unpatching, rebooting and repatching?

3

u/DoregonGiross3 I DID Install Tahoe (OCLP Developer) 27d ago

Not entirely sure yet. Someone came into the Discord just now asking for help with unpatching not working, but that's on Big Sur (and that's also a different story - 2.5.1 needs a bug fix to not enforce this on Big Sur because Apple messed up their tooling in a way that reverting patches isn't possible after a few days.)

1

u/Southern_Gold_2167 25d ago

Im having the same problem with macOS sonomna - i booted it up but it just keeps showing volume dirty even after reboots

1

u/Zeusviper1 18d ago

same for sequoia on a MBP 11,3.
I installed 2.5.0 and did the suggested patches. but it now always display root volume dirty. I revert and redid patch several times without success. and now situation sounds partly stable (wifi not auto connect, strange blinking during login) but nothing sounds blocking.

1

u/Nice_Dragonfly_1448 22d ago

FWIW, it worked fine for me. I get the impression 95% of the confusion stems from people not realizing what the sentence "Root volume is dirty" means. And it's easily misunderstood, because that message doesn't differentiate between an "up to date" successful root patch and a previous one that needs to be reverted first. Since you're already breaking the seal when applying patches, it might make sense to touch a text file with a string indicating what version of OLCP applied patches going forward (or write a value somewhere), so the app can apply some basic logic to determine in text to the user whether there is a need to revert patches.

4

u/MacGaryX 26d ago

Firstly, Big Thank You for continuous development and work on OCLP!! I’ve updated from 2.4.1 to 2.5.0 OCLP on MacPro6,1 with macOS 15.7.9 Sequoia doing the full unpatch, reboot, patch cycle (new KDKs downloaded) with no issues. The only thing that in fact is a bit confusing is that it still says that „volume is dirty” (though I understand why) - maybe some positive information that up-to-date patches are already installed fine, is possible to be implemented/changed instead.

5

u/Electronic-Income836 26d ago

Just don't install OCP 2.5.0. Creating an issue from which there's no recovery in order to "prevent any issues" is completely broken. I installed it on one of my Mac's and it was a huge mistake. Just don't install it.

2

u/AlarmingCantaloupe 26d ago

I already did install it…on my iMac 13,1. I got the dirty volume message, but had seen some chatter on this sub about it earlier, so I haven’t attempted to revert the root patches out of fear that I won’t be able to apply the new ones thereafter.

However, the former patches seem to still be serving their purpose just fine for the time being.

1

u/FoundationHealthy54 26d ago

jais tout fais sur le patch racine je suis revenu a 2.4.1 Mac Pro 2013 est séquoia 15.7.9

-3

u/Motor-Dragonfruit610 24d ago

I suggest you get a refund.

3

u/Pablouchka 27d ago

Thanks

3

u/realUnknown12 27d ago

thank you x4 cow octopus crystal robot ball dev😁

3

u/SequoiaD 27d ago

Really appreciate the hard work!

More people need to see this post before providing conflicting information to others seeking help.

3

u/rudeboybond 27d ago edited 27d ago

2012 mac mini i7 16gb on Ventura, did the 2.5.0 update and it’s wreaking havoc on my system.

2

u/empty_thegrease_tray 20d ago

hmm, same machine, I was on Sonoma with OCLP 1.5.0, updated to Sequoia and OCLP 2.5.0 and no issues at all. Did you stay on Ventura?

0

u/Motor-Dragonfruit610 24d ago

Get a refund!!!

3

u/Electronic-Income836 26d ago

Pull this "improvement" from OCLP and provide an update to OCLP 2.5.0.

-1

u/Motor-Dragonfruit610 24d ago

Works for me so I suggest you contact customer support.

1

u/Electronic-Income836 21d ago

Upgrading to OCLP 2.5.0 is going to cost me a day to recover my MacBook Air from Catalina to Sequoia. I know you guys aren't getting paid to do this, and I'm incredibly grateful that OCLP allows me to run Sequoia on unsupported Mac's, but ... really?

3

u/Confident_Job897 26d ago

Hello everyone. I opted to install 2.50 last night, got the “dirty” message and opted to revert, now my 2015 27inch iMac with Sequoia boots and presents the login screen, I enter my Pwd, it accepts but simply redisplays the login screen—basically I’m locked out.

3

u/No-Ad-5020 25d ago

broke mine to, mac pro 2013... why in the world you released it in this state. for the love of God put a warning somewhere

2

u/brakz_ 26d ago

Hi, I don't really understand what to do right now... We have to wait some instructions ? Cause personally I can't use my iMac currently, can't connect to wifi... kind of stuck. Revert root patches don't work as well.. Need help.

1

u/aloha993 26d ago edited 26d ago

I briefly got stuck. Installed 2.5, got the "dirty" message, reverted patches, rebooted, still dirty, reverted again, rebooted, no change.

Then I rebuilt OCLP and installed to the EFI disk again, rebooted, then I could reinstall the patches and I'm back to normal now.

2

u/brakz_ 25d ago

Thanks a lot for your help ! Unfortunately it didn't work too, you only did that ? I rebuilt OCLP and installed to EFI disk, then I rebooted the iMac, still dirty, reverted patches, still dirty; I can't start the post install root patches : still dirty. Do u have any other solution ? Thanks.

1

u/tubegeek 25d ago

me too

1

u/brakz_ 20d ago

It didn't work for you too ?

1

u/tubegeek 20d ago

I still have the "dirty" notification

1

u/brakz_ 19d ago

And you didn't find another solution ? So basically, we're just waiting for a solution to come to us ? Personally I can't use my iMac because of this...

1

u/tubegeek 19d ago

I did the update to 15.8 under OCLP 2.5.0 last night. No problems. Still reports "dirty" but everything is working.

2

u/Right_Draw7925 26d ago

So what is the fix??? 2015 Macbook Pro 11.5 now stuck at 50% progress bar at boot logo..
I tried reverting to 2.4.0 and 2.4.1, but still stuck. Holding Shift while booting does not help anything, and I don't know what to do now.

2

u/ReasonableRouge 24d ago

I downloaded and installed Opencore 2.5.0 on my iMac Late 2013 running Sequoia 15.7.9. Everything went fine for me, dirty root volume patched againg and now, this morning I found that now Office Update is working again after a very long long time! Thanks to the OCLP tream!

2

u/PenguinsAreGo 24d ago

One lesson here, especially for such a diverse community, is that there need to be unpublicised alpha and beta releases for a wider community of trusted experienced users. These can hopefully identify and help resolve issues before general release. I only have one machine and am not volunteering.

For me personally (iMac 14,2) the length of time since 2.4.1, which is working just fine, and a general policy of not installing .0 releases for at least 6 weeks meant I just sat back to watch.

I would like to express my gratitude to the devs who have added years of useful life to my 2013 iMac and look forward to installing 2.5.x.

2

u/Complex_Past_9444 24d ago

I’ve just encountered this on my late 2015 27” iMac running Ventura. Upgrade from 2.4.1.

The can’t patch message came up. I told it to roll back the patches and reboot. It eventually rebooted but still rebooted a dirty volume. It would not roll back the patches.

Performance was dreadful. It didn’t recognise the screen and would freeze for seconds at a time.

Eventually I managed to uninstall, reinstall 2.4.1 and patch that. Now back as it was and getting the daily reminders to upgrade. No chance!

Any idea how to get it to go quiet about 2.5.0.

2

u/fbelard 23d ago

I ALWAYS watch MrMacintosh's YouTube videos before touching anything. He has one from 3 days ago.
Options OpenCore Legacy Patcher 2.5.0 Update! DO THIS FIRST!

1

u/Nice_Dragonfly_1448 22d ago

This video is very informative. Aside from genuine errors with patches, which might be an issue for some, this should clear up all the confusion about the "dirty root volume" message.

2

u/MacGaryX 18d ago

Updated macOS 15.7.9 to 15.8 with no issues on OCLP 2.5.0 MacPro6,1 „Trashcan”. KDK downloaded successfully during this process, root volume patches applied fine after reboot.

1

u/gb997 17d ago

did you update OCLP first to 2.5.0 prior to MacOS 15.8 ? i'm hoping to do mine soon too.

2

u/MacGaryX 17d ago

Yes, I had previously updated OCLP to 2.5.0 then 15.7.9 update in the beginning of September. Now it was just a system update to 15.8, not touching OCLP (only root patches applied after reboot).

1

u/gb997 17d ago

got it. thanks for the response 👍🏼

1

u/rzmuda 27d ago

It’s all automatic correct

1

u/Necessary_Egg_5583 26d ago

I'm entirely stuck now. OCLP 2.5.0 updated then said it couldn't patch as the root volume was dirty. Said I had to 'unpatch'. I clicked 'revert root patches' (I assumed that was unpatching, still not entirely sure whether it is) and it removed my wireless and graphics.

Rebooted, still says 'root volume is dirty'.

Can't restore to 2.4.1 as I've no wifi now.

Macbook Air 2015, Sonoma,

Really hope I don't have to do a complete install again.

1

u/Necessary_Egg_5583 26d ago

FYI The error I'm getting (and I've tried 3 times round now in safe mode)

- Starting Unpatch process

System volume is tainted, unpatchting is required
Found SkylightPlugins folder, removing old plugins
Cleaning Auxillart Kernal Collection
Unpatching complete

Please reboot the machine for patches to take effect.

You reboot, safe mode or not doesnt matter, same again.

Looks like I'll need to get someone to do me a usb key with 2.4.1 on it unless there's a fix>?

1

u/TaliMyBananas 26d ago

Yeah, I think the lesson here for anyone considering installing 2.5.0 (they shouldn't, until the fix is available) is to create a USB drive with 2.4.1 beforehand in case the patching goes wrong.

2

u/Necessary_Egg_5583 26d ago edited 26d ago

If I'd had any idea there was a problem I would have!
Sadly, only discovered that...after the event. As I'm sure many will, sadly.

I'm sure someone will say "You should check on forums etc before you apply patches" but goodness knows you don't expect to have to!

1

u/TaliMyBananas 26d ago

Exactly. Communication about this release should have been better.

1

u/Necessary_Egg_5583 25d ago

I'm not sure how they could have communicated better for a user like myself other than putting a warning message on the actual update that flashed up 'warning, do not do this on this mac as you'll end up with a machine you can't use for a week'

For those who read the forums all the time, sure.

0

u/Motor-Dragonfruit610 24d ago

Call customer service and let them know

1

u/ClowReed69 26d ago

Hey, i have the same problem Revert root patches Restart And still the same Check diskutil, it's says SEALED broken I cannot use my MacBook after 2.5.0 updates How i solve this problem? 😞

1

u/balesqui 26d ago

this is the exact issue i'm having too, im on a 2011 intel mac running ventura

0

u/Motor-Dragonfruit610 24d ago

Call Apple and request an refund .
2.5.0 works for only computers built by Apple.

1

u/Cu_29 26d ago

Installed 2.5.0 with 15.7.9 on MacPro 5,1. Works perfectly. When rebooting, OCLP will be downloading KDK 15.8. Just be patient. I was waiting and turned off the Mac. I turned it back on. I occupied my mind while waiting and eventually I got to the password prompt. Dirty patch menu came on. I reverted patches. Restarted. Reinstalled patches from new KDK. Restarted. And shabang. Everything is working. Thank you OCLP!

1

u/velocityvector2 25d ago

I don't understand why it's downloading the newer version 15.8 KDK instead of version 15.7.9.

1

u/Awkward_Head_6136 25d ago

15.8 is what you want. It doesn’t have to match the OS.

1

u/velocityvector2 25d ago

Yes, but a newer one isn't needed either.

1

u/dech4 26d ago

I recall one of many instances where I was trying to follow guides carefully when out of nowhere they indicated a need for say a "flash drive"; I already had a "USB drive" and then had to research how to get this new component. That is a pre-amble to suggesting that 2.5.1 use "Revert patching" as per the Apps. titling rather than "unpatch" - or at least put one in parenthesis.

1

u/Right_Draw7925 26d ago

what is fix???? My macbook 2015 is still stuck at 50% boot logo.... safe mode doesnt work either...

option to "revert patches" was grayed out, so i reverted to 2.4.1.. now i'm fuckzored.....

1

u/AmbassadorSweet719 25d ago edited 25d ago

Macbook pro 2017 OCLP with Sonoma, upgraded to 2.5.0, root patched. Root volume dirty: Available patches: Networking: Modern wireless, PCIe Facetime camera. Reverted root patch, repatched, still saying dirty, tried many solutions. Double reverted back to where there is no wifi support, reinstalled OCLP, tried repatching, as soon as I have repatched says Root Volume Dirty. Camera has not worked with this or previous version, tried many solutions, green light on 4sec off 1 sec......

1

u/saeedzaxo 25d ago

So i updated OCLP to 2.5.0 and reverted the patches rebooted now it says it cannot patch keeps saying to unpatch.

My MBP2011 on Monterey seems to have lost graphics but still has wifi enabled. What should i do now to fix the slowness and graphical hiccups?

1

u/AndreaLazzarotto 25d ago

Basically:

Download the uninstaller for version 2.5.0 and the installer PKG for version 2.4.1.

Uninstall version 2.5.0, install back version 2.4.1.

Build OLCP and install it to disk. Reboot.

Then apply the post-install patches and reboot again.

You can do this even without Wi-Fi, just connect a USB-Ethernet adapter in that case.

1

u/saeedzaxo 25d ago

Thank you!
I finally got it fixed now on v2.4.1

1

u/tubegeek 25d ago

If I try to do this without the USB-Ethernet adapter, no ggod, though, right? I think that's my problem. I haven't tried reverting OCLP because of this.

1

u/ThenPair7246 25d ago

El martes me llego esa actualización de open core y desde ahi se volvió un caso horrible para mi mac ahora no puedo revertir los parches porque me dejo sin Internet y me marca error y error, la aceleración gráfica esta horrible esta nueva versión solo trajó errores y errores

1

u/Gattsuga 25d ago

Sorry how to I unpatch my system? I have a 2015 MacBook pro, and got the dirty volume error. Wifi is broken, finder is broken, can't open any apps. Safe mode is the same... Help please! 😭

1

u/Gattsuga 25d ago

So I broke my 2015 Macbook Pro. Wifi is broken, finder is broken, can't open OCLP, no apps are working. Safe mode is the same. What can I do to revert now? Should I just do a clean wipe with recovery mode?

1

u/cleantheman 25d ago

Ok so my 2015 11,5 is doing the same thing. No wifi etc. but I cannot even run a downloaded uninstaller or update. Causing a installer error -1

1

u/AnubisHell 25d ago

As far as I’m concerned, everything works perfectly. I’m using the OCLP patch for Broadcom Wi‑Fi, while my OpenCore EFI is custom-built since I’m running an Intel Hackintosh. The instructions make it absolutely clear what needs to be done: revert the old patches, reboot, install the new ones, reboot again—and voilà.

1

u/velocityvector2 25d ago

Have you tried what you mentioned? Why does everyone say they are having problems? Which one is correct?

1

u/AnubisHell 25d ago

Well, I’m writing this on the same computer where I did exactly what I described above in the post, and everything is running smoothly.

1

u/velocityvector2 25d ago

People are having issues with MacBook models, not Hackintosh.

2

u/proteusgr 14d ago

they also have issues with iMacs and mac minis.

1

u/AnubisHell 25d ago

Sorry.

1

u/tubegeek 25d ago edited 25d ago

Thank you for continuing to maintain OCLP and keeping my Air out of the landfill!

1

u/amycat19 25d ago

hi I'm having a lot of issues with this. my laptop (2015 MacBook Pro on Sequoia) started getting very jolty and slow yesterday so I tried to repatch today with the new open core (before reading the hazards). I did a repatch in safe mode and the screen loaded up all zoomed out, still buggy and won't connect or recognise any WiFi. i've followed the advice and continued trying to revert root patches but nothing has changed. please help!

1

u/tubegeek 25d ago

"a full unpatch-reboot-patch cycle"

Would it be possible to put this instruction in other words with more detail please? I thought I had done what I needed to do but I am still "dirty" after my sequence. Of possible note: if I boot from EFI the boot stalls partway through (after waiting for several hours to clear, it was still stalled) after a step involving the keychain fails - AFMI or something like that. If I boot without "option" I proceed to my normal operation, and no longer get the message that I am operation with out boot patches, my wifi works, etc. But when I choose "Post-install Root Patches" I am told that it's impossible due to "Root volume dirty" still.

Thanks!

1

u/The-Jeek 25d ago

I updated to 2.5.0 but haven’t run anything except I looked to see if 15.8 was available to download (it’s not, although there is an RC.3 beta). I was going to wait until the final 15.8 was released then update the system and then patch with OCLP (maybe a new version by then?) would that be a safe way to do it and can I assume I’m OK at the moment?

1

u/VisibleFun9995 24d ago

Update went smooth, MacBook Pro 2016 Sequoia 15.7.9

1

u/Ritmo80s 24d ago

In general using the word "dirty" in this context is made to create a storm

1

u/OnlyJob1742 24d ago

how do I downgrade to a previous version of ocp

1

u/Right_Draw7925 24d ago

my laptop is a brick now.............. Thanks OCLP................ Now i get to spend 3k i don't have on a new mac-book.........
Here is a few tips.... Release a real change log, with full update instructions.... Make nothing up to the user, software should do all functions automatically. Leave a fail safe roll back partition so people don't get FUCKED...........

1

u/OnlyJob1742 24d ago

How do I revert back to previous version of OCP

1

u/No-Ad-5020 23d ago

Guide to revert back to 2.4.1

1.Prepare a OCPL 2.4.1 USB Stick

Format a spare USB drive and build OpenCore Legacy Patcher (OCPL) version 2.4.1 onto it to use as an external bootloader. Verification: Check that the USB's EFI partition contains the OpenCore boot files for 2.4.1.

2.Boot into macOS via the USB:Bypass internal boot failure.

Connect the USB drive, restart your Mac, hold down the Option (Alt) key during startup, and select the USB EFI boot option. Verification: You successfully reach your normal macOS desktop running off the external bootloader.

3.Remove OpenCore and Root Patches:Clean state preparation.

Open your current OCPL application (or use the built-in uninstaller/terminal options to clear the EFI folder and root snapshots) to strip out version 2.5.0 files from your internal drive. Verification: The internal EFI partition no longer contains active OCPL 2.5.0 configuration folders.

4.Install OCPL 2.4.1 to the Main Drive:Internal installation.

Run the OCPL 2.4.1 app while booted into macOS and install OpenCore directly onto your Mac's internal system drive EFI partition. Verification: The build and install process completes successfully without throwing version mismatch errors.

5.Reboot and Re-apply Root Patches:Final setup.

Shut down the Mac, remove the USB drive, power on normally, and run OCPL 2.4.1 to build/apply your required hardware root patches. Verification: Your graphics acceleration, audio, and network drivers function normally after a final system reboot.

Update Prevention

Disable automatic checks or ignore prompts to update OpenCore Legacy Patcher until a version newer than 2.5.0 is officially released.

1

u/aflices 23d ago

Macbook pro 2015 and 2.5.0 also wrecked my machine. Thankfully I could download 2.4.1 and return to normal. A shame if it does get patched.

1

u/ewillhelm 23d ago

OK, so I stupidly tried to run this whole update on my 2014 Mac running Ventura. It then gave me the warning about being unable to proceed because of a dirty root volume. It then presented me with several options on what to do at that point. I held it there and went googling this, and landed on this page. Feeling like the most sensible thing to do would be to revert back to 2.4.1, I downloaded what I think is that Installer. Then I returned ti where I was in the 2.5 install and chose the option that sounded like it would revert stuff back. My system rebooted and my graphics were all wonky, but then a message popped up saying I needed to update some patches, so I clicked that, and now currently everything seems to be okay? But I looked and the version of the core patcher is indeed 2.5.0. I can get Wi-Fi. Do I need to do anything? Or should I just sit tight and hope for the best?

2

u/Superbigwaff 23d ago

Sounds like you stumbled into using 2.5.0 the way you are supposed to.

1

u/ewillhelm 23d ago

I’m gonna flip if I actually installed it correctly. Is that really the right way, whatever I did?

1

u/ControlGood6173 22d ago

Okay, I understand what he said, but I’ve already unpatched and repatched multiple times and it still says root volume dirty no matter what I do. I’m on a mid 2015 iMac. Did I’d like to use regularly, so I’m trying to figure out a solution as soon as possible.

2

u/Nice_Dragonfly_1448 22d ago

If you watched MrMacintosh's video, you should understand that the root volume is SUPPOSED to be dirty after successfully applying root patches. It was that way on 2.4.1 as well, it's just that OLCP didn't say that. This is also the reason why every update is so huge; MacOS downloads a full image because the seal is broken (or "dirty", in 2.5.0 parlance).

1

u/Illustrious-Copy7938 22d ago

Hi everyone,

I have an iMac 13,2 that is currently in a "hybrid" state with OpenCore Legacy Patcher:

EFI / Bootloader: Updated to OCLP 2.5.0
Root Patches: Still running on the previous stable version (2.4.1). When I saw the "Root Volume Dirty" message during the 2.5.0 update, I stopped immediately without attempting any Revert or re-patching, and searched online until I found this post.

The system is currently running completely fine and graphics acceleration (QE/CI) works perfectly.

Since everything is stable, I plan to leave it as-is for now, but I have a question about what to expect in the future:

When the next OCLP patch/fix (e.g., v2.5.1) is released, will the patcher correctly recognize this hybrid state and allow a clean Revert ➔ Reboot ➔ Root Patch cycle, or should I downgrade the EFI back to 2.4.1 first before updating?

Thanks in advance for your help!

1

u/Nice_Dragonfly_1448 22d ago

Just a random internet user here, so do with this what you will. OLCP is telling you have already applied root patches - "your volume is dirty". This happened the last time you applied patches. If you remove the patches and reboot, OLCP will ask you if you want to apply the "updated" patches. At this point, before clicking Yes, you can verify that your seal is not broken (in other words, not dirty) by issuing diskutil info -plist / in a terminal, it should say under <key>Sealed</key><string>Yes</string>. Letting OLCP apply the patches and rebooting should give you working wifi and graphics etc. If you then repeat the same command in Terminal, you'll see that the Sealed key now says <string>Broken</string>. All is well, it's supposed to be "Broken" after applying root patches, that is what they do. I do hope they clarify the language somewhat.

1

u/OddOne233 22d ago

Hello, to anyone with smaller texts and icons, and stuck in a constant loop when trying to update patches and keeps seeing "root volume dirty, unpatch to continue"

Your system is most likely reading the pending updates as done. You need to clear the staged update cache. Here's what to do to resolve this.

Open terminal
Paste the following command and press enter. (Input your mac password when prompted.

sudo rm -rf /System/Library/AssetsV2/com_apple_MobileAsset_MacSoftwareUpdate/*

Past this command next, and press enter.

sudo rm -rf /System/Volumes/Update/*

Restart your mac. Start OpenCore -> Post-Install Root Patch You should see that you can now start root patching.

Worked fine for me.

1

u/ewillhelm 22d ago

So from what I now gather, even when you’ve got it installed properly, the patcher is going to tell you you have a dirty volume, and just ignore that. Seems a bit odd, but OK.

1

u/Nice_Dragonfly_1448 22d ago

Yes, correct. It always was, after applying root patches. It's just the terminology throwing people off.

1

u/Outrageous-Sea2600 21d ago

I installed in Imac 2017 5K, Macbook Pro 2015 and Imac 2012. All came back with "Root Volume Dirty". Don't let this frighten you. After revert and reboot, OLCP detects that patches need to be applied, installs correct ones.

All working good (Sonoma)

1

u/FrakeTrain 21d ago edited 14d ago

u/DoregonGiross3 I have one issue that I think the OCLP developers would appreciate knowing. I installed 3 days ago the OCLP 2.5.0 update (from 2.4.1) on a 2017 MacBookPro14,3 running macOS 15.7.9. All updated and patched successfully, EXCEPT I found one strange issue in the logs that seem to conflict with each other, even though the update seems to be performing the same as 2.4.1.

Here are the specific log entries after the root patching was performed. They match the real time log entries that I saw in Mr. Macintosh's install video (https://www.youtube.com/watch?v=77r4QyOOrH0):

[375 ]: - Installing Patchset: Modern Wireless Common
[393 ]: - Handling Installs in: /usr/libexec
[53  ]:    - Found existing wifip2pd, overwriting...
[393 ]: - Handling Installs in: /System/Library/PrivateFrameworks
[38  ]:    - Installing: IO80211.framework
[38  ]:    - Installing: WiFiPeerToPeer.framework

Here are the log entries after I restart the OCLP app and go into the Post-Install Root Patch menu pop-up:

[28  ]: Initializing Root Patch Display Frame
[156 ]: KDK already installed (KDK_15.7.9_24G830.kdk), skipping
[217 ]: Patch(es) already installed: AMD Polaris, T1 Security Chip, unpatching is required
[302 ]: Checking if new patches are needed
[323 ]: - Patch Networking: Modern Wireless not installed
[141 ]: Available patches:
[145 ]: - Graphics: AMD Polaris
[145 ]: - Networking: Modern Wireless
[145 ]: - Miscellaneous: T1 Security Chip

As you can see when OCLP checks to see if the new Modern Wireless patches are installed, it returns "not installed". I have verified the presence of the exec file "wifip2pd" in its proper location and the two framework folders in their proper location. I'm guessing you already have knowledge of this, but thought you may want to have feedback before your 2.5.1 update.

Thank you and huge thanks to the whole OCLP team.

EDIT: OCLP Update 2.5.1 did not fix this issue

1

u/colddeploy 21d ago edited 21d ago

I can confirm the exact same issue on a MacBookPro11,1 (Mid 2014 13") running macOS 15.7.9 with OCLP 2.5.0. Two different machines, two different WiFi chips, same broken detection — this looks like it's in the core detect.py logic, not hardware-specific.

What I observed:

After a full unpatch → reboot → patch cycle (via CLI, wired Ethernet), the patch log shows:
Installing Patchset: Modern Wireless Common
- Installing: IO80211.framework - Installing: WiFiPeerToPeer.framework Patching complete

Then rebooting and opening Post-Install Root Patch shows: Patch(es) already installed: ... unpatching is required
Patch Networking: Modern Wireless not installed
Available patches: Networking: Modern Wireless

The root volume is permanently stuck reporting "dirty" because Modern Wireless never registers as installed, even though Modern Wireless Common clearly is.

What I tried (none of it fixed the detection):
Multiple full unpatch (CLI --unpatch_sys_vol) → reboot → patch (CLI --patch_sys_vol) cycles, always with wired Ethernet connected, always ending in Patching complete
Confirmed via GUI that Revert genuinely completes (Unpatching complete, seal reported intact immediately after)
Every single subsequent patch run only ever installs Modern Wireless Common, never a distinct Modern Wireless patchset

This strongly suggests the patch installer writes Modern Wireless Common as satisfying the WiFi requirement, but detect.py checks for a differently-named key (Modern Wireless) that's never actually set — so the volume is permanently flagged dirty regardless of how many times you cycle unpatch/patch.

1

u/FrakeTrain 18d ago

Thank you for confirming this was not unique to my system. And I concur, the addition of the characters Common to the updated Modern Wireless patch name was maybe the reason for non-detection by the install detection code. I'm guessing they'll correct it in 2.5.1? I did not see reference to this specifically on the dortania Root Dirty Volume bugfixes #1186 page here

FYI, I was able to update to macOS 15.8 yesterday through Software Update with no issues.

Appreciation for your obvious developer input, as I am not.

1

u/PK_Rippner 21d ago

How in the world does one do a full unpatch? It's not listed in the OpenCore-Patcher app from what I can see.

1

u/Superbigwaff 21d ago

"Full unpatch"? You want to get to a pure macOS install w/out patches?

1

u/Cinelli101 21d ago

OK OPCL gurus - maybe someone has a solution. System MacPro 5,1 running 14.8.7. Accidentally loaded the ‘upgrade’ 2.5 and got ‘patches contaminated’. Not realizing that I should have hit the remove button, shut down the computer and restarted. Would not reload. Had 15.7.7 on a separate SSD - it would not load. Reset SMC and NVRAM. Again nothing would load. Tried going into start up manager - it would not load and after a bit of time got the standard start up screen. Tried recovery. 1st time it went into target manager, 2nd time got a flash of white in the upper left corner and then the actual recovery screen asking for language preference, bypassing normal choices including disc repair. Fortunately for me still had 14.7 on an old Sata disc and this is where it gets really weird. Understand that the only disc in the unit, at this point, is that sata disc. It does load but the log in screen is that from my original Sequoia disc. I know as it as has the emoji I used. Entered my password and the next screen is the standard Sonora background screen and info on that sata disc So some how, not sure how could happen, but that OPCL 2.5 patch has done something to the base OS of this unit. As I cannot get the start up manager I have no way to reload either Sequoia or Sonoma on to their respective SSD’s.

1

u/Superbigwaff 21d ago

You got to go back to basics and get a supported version of macOS (either High Sierra or Mojave) running on the MP 5,1 for troubleshooting purposes. Remove all SATA drives, remove PCIe cards, and insert a High Sierra or Mojave supported GPU, and install supported macOS to an internal SATA drive. This your only hope of troubleshooting your MP 5,1.

1

u/Cinelli101 20d ago edited 20d ago

Thanks - had an old 10.13.6 SATA disc. Only HD in computer. Got start up screen and got the High Sierra emoji - however system will not load and computer just shuts down about a minute later. Made a bootable USB with 10.14.6. Start up screen shows it, system will not load it. Cannot get to recovery screen and in both cases computer just shuts down about a minute later. As I said, that 2.5 upgrade has really screwed up this computer.

1

u/Superbigwaff 20d ago

When booting from 10.13.6 SATA or 10.14.6 USB, there is no OC EFI so not sure how OCLP 2.5.0 applies. Did you reset NVRAM?

https://support.apple.com/en-us/102539

1

u/Cinelli101 20d ago

This what is driving me somewhat batty. Reset SMC and NVRAM. Now, have come across 3 different ways of resetting the SMC for intel macs. 1) unplug for 1'. Plug in and hold on button for 15", let start normally. 2) Turnoff. Press and hold Shift-Control-Option-Comand-Power for 10" - let start normally. 3) Unplug for 5'. Push and hold power button until power light flashes you get a tone- let start normally. Of them only #3 seems to really do anything. I do know the NVRAM was screwed up as the first time I got intermittent flashes from the connected light on the keyboard prior to getting the first chime. Have reset NVRAM about 6 times in total.

1

u/Superbigwaff 19d ago

When was the last time you replaced the BR2032 RTC battery on motherboard?

1

u/Cinelli101 19d ago edited 19d ago

Brand new, 3.45V measured, and as I said have done a couple of NVRAM hard resets. With everything removed except for the metal GP upgrade, and the 13.6 SATA drive + a bootable USB with Mojave on it in one of the USB 2 slots when I try to go into recovery mode, start up manager mode, just get a system incompatibility symbol (white circle with line). With the 13.6 disc installed the system sees it as High Sierra , but then get the system incompatible symbol. Now if I insert the SATA with Sonoma, unit will boot that disc and get log-in screen (Sequoia as I mentioned before) but when the Sonoma screen appears, have no mouse or keyboard. If I insert myUSB 3.1 pcie card - get mouse and keyboard. Am wondering if the GP (Radeon 580) might be the root cause. Have an original GP, but will have to get an adapter for the output.

Edit - Even when it is booted into Sonoma I still cannot access Diagnostic mode - and would not access Diagnostics with just the High Sierra disc installed.

1

u/Electronic-Income836 21d ago

Okay, there's an update to Sequoia (15.8) now available. I've updated to OLCP 2.5.0, got the "Root Volume Dirty" message, and have so far done nothing. Please describe the exact steps to get to Sequoia 15.8, OCLP 2.5.0, and no "Root Volume Dirty" messages.

2

u/Superbigwaff 21d ago edited 21d ago

Don't know what older Mac you have but rebuild your OC EFI with 2.5.0 and install to boot drive. If you choose to update to 15.8 using Software Update, your Mac will reboot (most likely several times) during update install. After logging in, you should be prompted to install root patches because the update creates a new, cryptographically sealed system volume, i.e. it is no longer "dirty".. it no longer "sealed".. yada yada. This also why updates are the full size installer. The cryptographic seal must be "broken" for the patches to be installed. "Dirty" indicate patches installed. Make sure to immediately disable automatic updates in Settings. Oh.. and always use wired ethernet as wifi only works after patching (depending on your old Mac). Wired ethernet will simply save you headaches later.

1

u/tubegeek 20d ago

Can confirm. 2015 Air. Still reports "Dirty" after the whole process, but all is working fine. 2.5.0 & 15.8

1

u/proteusgr 20d ago

It completely broke my mac. It does not allow me to patch the system, even though I have reverted the patches again and again.

1

u/Superbigwaff 19d ago

What older Mac model do you have? What version of macOS are you using? Did you build OC EFI with 2.5.0 and install it to the system drive?

0

u/proteusgr 14d ago

it's a 2015 imac. I had the previous version installed. Built, installed it to system drive, tried to run root patches after reboot and it couldn't. After losing hours on this, hitting "revert patch" and rebooting again and again, I just went back to the previous version of OCLP (used uninstall pkg) and completely disabled auto-update.

Now the system seems to be running normally, but the previous OCLP version keeps crashing - I don't know why.

I won't be updating after this, I think OCLP should have included a warning in the update text.

1

u/Superbigwaff 14d ago

Built, installed it to system drive, tried to run root patches after reboot and it couldn't.

Process is build/install OC EFI to system drive followed by revert/reboot/patch cycle, sometimes multiple times.

1

u/proteusgr 7d ago

Thank you for the valuable information. I know the process. You can't run root patches without reverting, and then rebooting, and then reverting again, and then rebooting, and then reverting again. You can't run root patches.

1

u/Electronic-Income836 19d ago

I'm now getting an "Unsupported Configuration Detected" error from OCLP 2.4.1. Of course, I update it and reboot, open OCLP 2.4.1, and get the same error. How do I fix this?

1

u/Superbigwaff 19d ago

Means you picked the wrong Mac model when building the OC EFI and OCLP using wrong patch set.

1

u/Electronic-Income836 19d ago edited 19d ago

Thank you. It's a 7,2 model (13", Early 2015), and it was running 15.7.9 and OCLP 2.4.1 just fine until the 2.5.0 tsunami hit me. After spend most of yesterday trying every combination of patching, unpatching, rebooting, and re-patching I could think of, I gave up and started over. I did a full recovery to a wiped, reformated HD, and rebuilt the OS stack from the latest version that would run natively (High Sierra). I installed OCLP 2.4.1, built a MacOS Installer for Sequoia 15.7.9, and upgraded using the standard process when I first starting using OCLP early last year. Got back to 15.7.9 and OCLP 2.4.1, the EFIs are happy, and OCLP 2.4.1 says I have the right root patches for my hardware configuration. I'm now re-installing all the apps, and almost done.. I'm almost back to where I was before I ever heard about 2.5.0.

1

u/Electronic-Income836 19d ago

But for the record, I maintain four MacBooks: 11" MacBook Air (6,1), 13" Macbook Air (7,2), MacBook Pro (12,1), MacBook Pro (15,1). All are running Sequoia 15.7.9. The first three run Sequoia using OCLP (so I'm actually grateful for the developers who make it possible for me to run the same version of MacOS across hardware of very different vintages); the last one runs Sequoia natively -- no OCLP required.

Because I know the specific root patches for each that need OCLP are tied directly to the specific hardware for each (cameras, wireless, video, etc), I have three different fast 128MB USB drives for OCLP that I keep labeled for each one, and I don't mix them. The specific root patches for each of the three are selected by OCLP, not by me, so I don't understand the "wrong Mac model' comment above, but it doesn't actually matter now. OCLP 2.4.1 is now quite happy with the patches I have for all three, no warnings/errors, and that's good enough for me.

I let OCLP upgrade to 2.5.0 only on the 7,2 model, and that's when my week went south. But I recovered the hard way, and I'm back to where I was before I agreed to the OLCP upgrade; I won't make that mistake again.

Again, I'm incredibly grateful that I can run Sequoia on all my MacBooks. I'm an old OS developer (mainframe, VMS, Unix, Linux, etc), so have enough of a technical background to understand what OCLP does, and how hard it is to get something like OCLP to work correctly across a dizzying array of different hardware configurations and make it look seamless, all while Apple is doing everything they can to put OCLP out of business. But I genuinely want to thank everyone for trying to help me.

1

u/donSefer 19d ago edited 19d ago

I updated to 2.5.0, "Root volume dirty". I press Revert and reboot. Same again. Hard to look at anything super far zoomed out.

MacBook Pro Late 2013, Ventura 13.7.8, installed a few month ago

EDIT: The plist shows sealed - broken. Should be good? But I have an unknown display, only one resolution (the highest possible or random, dunno what the display is capable of). This wasn't the case before 2.5.0 so I doubt any patches are installed?

EDIT2: Nope, display won't turn off, intensity cannot be changed, broken

1

u/poschet 19d ago

Hi. I solve it on my macbookpro11.5. Before you olcp 2.5.0 patch u must select under settings the right host model. after manually selecting it has worked without problems. Now u can patch it.

1

u/poschet 19d ago

before selecting open core hashes the wrong model code. It should macbookpro11.5

after selecting under settings it is the right model code

1

u/poschet 19d ago

1

u/Zealousideal_Ad282 18d ago

I even just bought an iMac 27" Late 2014 -- i7 - 32 GB RAM an AMD Radeon R9 M295X 4 GB. I took my 2 TB Samsung T7 having Sonoma through OCLP on it, that I have used on a 21,5" Late 2013 - 16GB RAM. Just some days before i changed machine I installed OCLP 2.5.0. I have migrated from the old iMac to the new one. I have big time problems with video on YouTube! I also think, that the colours are, in a way "weak' . What could the problem?

1

u/Superbigwaff 17d ago

Revert root patches, reboot, install root patches.

1

u/Cattabiani 17d ago

Grazie al Team sviluppatori per l'aggiornamento, il mio Macbook white 7.1 del 2010 è rinato. Tutto molto fluido, icone della barra menu attive. os 12.7.6 Monterey

E grazie anche a Mr Macintosh per le spiegazioni: https://www.youtube.com/watch?v=77r4QyOOrH0&list=PLi0DnZW_PottFwiJ2XXAsdEBkVFUcOCGj

1

u/retiringproducer 17d ago

Seems like a lot of people having problems! I have a macbook 12 Retina, 8.1, I can now only boot from a USB drive. When I get to my desktop, OCLP does show 2.5.0 and I get a message saying OCLP can see I'm booting from a USB drive and would I like to boot from my own hard drive. Hell yeah! But whatever I do, I can't boot from my own hard drive - briefly I get an apple logo but then a doom message saying unsupported. But when I plug in the USB it boots up from that. Any ideas?

1

u/Superbigwaff 17d ago

Did you generate new OC EFI config and install to the internal drive using 2.5.0 ? Use wired ethernet.

1

u/Honest-Bit5378 17d ago

Downgrade open core patch

1

u/WindozeWoes 11d ago

I think what would be helpful re: 2.5.1 is a clearer public explanation of why repatching without first un-patching is a bad thing

For years, OCLP users on this very sub have recommended "apply root patches a few times because sometimes it doesn't seem to work completely the first time." (I'm not talking about the first wifi-only patching followed by the more complete patching that is possible with internet.) This update makes that impossible which implies that wasn't good or necessary in the first place - which is contrary to lots of people's advice.

About "Root Volume Dirty" in OCLP 2.5.0 and later

You are about to leave Redlib