Incompatible Driver(s): tib.sys?
We are using Acronis from 2006 to replace Symantec Ghost. This is what Acronis do best taking OS (C: drive)Image while computer can be used (Good for Servers OS) with full explorable image file.
Reading through the conversation started in Sep 2021. I could see only ONE work around, from Steve Smith all the rest is nothing but comments on Acronis Passive respond! Acronis, this is not good enough for such critical application.
ps: Steve suggestion worked for me on Lenovo T490 with W11 pro.
Seca Hattin wrote:Whats the Problem?
Why can't we just have an instruction, how to uninstall tib.sys for those who want to activate MS Memory integrity in Windows 11?
The only drawback after this would be not to able to explore inside an image any more, or not?
----------------------------1, Open task manager and disable across from startup apps.
2, Restart Windows.
3, Open the next holder.
C:\Windows\system32\DRIVERS\
4, Then you can delete the following files.
tib.sys
5. Open task manager and set it to start across.
6. And turn Memory Integrity back to ON.
7.Restart your computer.
Atsushi Kushida wrote:Seca Hattin wrote:Whats the Problem?
Why can't we just have an instruction, how to uninstall tib.sys for those who want to activate MS Memory integrity in Windows 11?
The only drawback after this would be not to able to explore inside an image any more, or not?
----------------------------1, Open task manager and disable across from startup apps.
2, Restart Windows.
3, Open the next holder.
C:\Windows\system32\DRIVERS\
4, Then you can delete the following files.
tib.sys
5. Open task manager and set it to start across.
6. And turn Memory Integrity back to ON.
7.Restart your computer.
Hello Atsushi!
Could you please tell us what issue are you facing or that solution you quoted helped to solve it?
Thanks!
Hello Atsushi!
Could you please tell us what issue are you facing or that solution you quoted helped to solve it?
Thanks!
Hi Lose
In Windows 11, I got an Incompatible Driver (tib.sys) warning, so I deleted the driver. Many people have trouble with this driver. It's the only way to use older versions across.
Jules van Rosebrook wrote:Same problem 'Incompatible Driver(s): tib.sys' I am amazed by the lack of support from Acronis, I expected better.
Hello Jules.
Please check our page regarding the support for the ATI 2020: https://www.acronis.com/en-eu/support/lifecycle/consumer/ ( ended in 2021 ).
I've commented the issue with the team.
Thanks in advance!
My understanding is that as ATI 2021 and earlier are long out of support that Acronis will not be issuing an update to overcome this problem. I have made numerous representations to Acronis to no avail.
Ian
To summarise this topic:
Acronis Try & Decide kernel driver tib.sys is incompatible with Windows Core Isolation / Memory Integrity feature found in Windows 10 and 11.
With ACPHO, there is an option to perform a Custom Install and deselect Try & Decide.
With ATI 2015 - 2021, there is no such option, Try & Decide is installed by default, therefore the methods to remove this require either editing / changing the Windows Registry, or else renaming or deleting tib.sys. Those actions essentially require booting Windows into Safe Mode to be performed manually. It is possible to make these changes using PowerShell but a Windows restart is still needed to unload any active service after doing so.
Steve Smith wrote:To summarise this topic:
Acronis Try & Decide kernel driver tib.sys is incompatible with Windows Core Isolation / Memory Integrity feature found in Windows 10 and 11.
With ACPHO, there is an option to perform a Custom Install and deselect Try & Decide.
With ATI 2015 - 2021, there is no such option, Try & Decide is installed by default, therefore the methods to remove this require either editing / changing the Windows Registry, or else renaming or deleting tib.sys. Those actions essentially require booting Windows into Safe Mode to be performed manually. It is possible to make these changes using PowerShell but a Windows restart is still needed to unload any active service after doing so.
That's totally correct. And thanks for summarizing.
I will leave the KB https://kb.acronis.com/content/70782.
Thanks to everyone!
My recollection is that Try & Decide was not included in ATI 2015 (it is not mentioned in the user guide). Probably because ATI 2015 uses a significantly different approach to ATI 2014. I believe it was reintroduced in ATI 2016.
Ian
I just started to have this same issue. Win11, ATI21. I renamed lib.sys and now my list of incompatible drivers is empty and memory integrity will still not turn on. I see another member had the same issue but did not see a resolution. Any ideas? TIA
I just started to have this same issue. Win11, ATI21. I renamed lib.sys and now my list of incompatible drivers is empty and memory integrity will still not turn on. I see another member had the same issue but did not see a resolution. Any ideas? TIA
I fixed it with this method:
1) Run regedit and export [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tib]
2) In regedit delete the folder tib
3) Reboot PC and enable Core Isolation - Memory Integrity.
4) Click the File you created in step 1 above to restore the registry entries. (May get an error but ignore)
5) Reboot PC and Core Isolation - Memory Integrity stays set and tib.sys is also enable and everything seems to work Ok.
Thank you. I will try this when I get home and report back.
Billybigun, can you please tell me what is the value of the Start data item under the ...Services\tib registry key?
Billybigun wrote:I fixed it with this method:
1) Run regedit and export [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tib]
2) In regedit delete the folder tib
3) Reboot PC and enable Core Isolation - Memory Integrity.
4) Click the File you created in step 1 above to restore the registry entries. (May get an error but ignore)
5) Reboot PC and Core Isolation - Memory Integrity stays set and tib.sys is also enable and everything seems to work Ok.
Bummer, it did not work for me.
Interesting that it's still not fixed even in the new product. I was just looking to either update Acronis from 2019 or find a new solution, new solution it is I guess.
markdavidwood wrote:Interesting that it's still not fixed even in the new product. I was just looking to either update Acronis from 2019 or find a new solution, new solution it is I guess.
Hello Mark.
The lifecyle of Acronis True Image 2019 is expired and any updates will be performed on that product: https://www.acronis.com/en-eu/support/lifecycle/consumer/#true-image
Regarding the Acronis True Image Home office it works following the instructions of this KB: https://kb.acronis.com/content/70782 ( disabling Try & Decide ).
Thanks in advance.
Acronis is using this driver conflict to eliminate all our paid licenses in an effort to sell us on buying a subscription service.
Since I paid for a "Perpetual License", this is their way to attempt to force me into re-purchasing.
Perpetual = forever. Obviously, they have placed profit over customer loyalty.
I will NOT be purchasing additional products from a company that treats me that way.
Unless, of course, they reconsider and fix this one driver causing the issues "tib.sys" driver
Lisa Cross wrote:Acronis is using this driver conflict to eliminate all our paid licenses in an effort to sell us on buying a subscription service.
Since I paid for a "Perpetual License", this is their way to attempt to force me into re-purchasing.
Perpetual = forever. Obviously, they have placed profit over customer loyalty.
I will NOT be purchasing additional products from a company that treats me that way.
Unless, of course, they reconsider and fix this one driver causing the issues "tib.sys" driver
Hello Lisa,
Thank you for your message. I have relayed it to our team.
I would like to inform you that Acronis True Image 2020 has reached its end of lifecycle since 2020. Therefore, any updates or support for this version have ceased several years ago.
I would also like to clarify that we are not attempting to sell you any product or impose anything on you. The memory integrity feature is not supported on outdated versions of our product.
To address your concern, I recommend referring to our knowledge base article at https://kb.acronis.com/content/70782 and following the suggestions provided there.
Thank you for understanding.
Jose Pedro Magalhaes wrote:Lisa Cross wrote:Acronis is using this driver conflict to eliminate all our paid licenses in an effort to sell us on buying a subscription service.
Since I paid for a "Perpetual License", this is their way to attempt to force me into re-purchasing.
Perpetual = forever. Obviously, they have placed profit over customer loyalty.
I will NOT be purchasing additional products from a company that treats me that way.
Unless, of course, they reconsider and fix this one driver causing the issues "tib.sys" driver
Hello Lisa,
Thank you for your message. I have relayed it to our team.
I would like to inform you that Acronis True Image 2020 has reached its end of lifecycle since 2020. Therefore, any updates or support for this version have ceased several years ago.
I would also like to clarify that we are not attempting to sell you any product or impose anything on you. The memory integrity feature is not supported on outdated versions of our product.
To address your concern, I recommend referring to our knowledge base article at https://kb.acronis.com/content/70782 and following the suggestions provided there.
Thank you for understanding.
I just read through this entire thread. Jose, it appears that you didn't even bother doing that when you first responded on April 4th. This latest response to Lisa is complete garbage as well ... ATI 2020 did not reach it's end-of-lifecycle in 2020 (although it did in 2021 Acronis Support Lifecycle Policy for Consumer Products).
The fact that memory integrity is not supported in the 2020 version of ATI is part of the entire point of this thread, which you might have realized if you had bothered to even read. This thread was started in September of 2021 which means that technically support had ended the previous month, but issues with memory integrity go all the way back to the Windows 10 April 2018 Update when it was introduced ... and Acronis continued to release new versions of their product (including the 2020 version 16 months later) which did not address the issue, yet marketed them as being compatible with Windows.
It's total BS and reminds me of when Windows 10 was first released ... the version of ATI purchased the previous year was incompatible and the only options were to update to the new version (less than 12 months later) or stay on Windows 7). I was pissed about that, but it pales in comparison to this current insanity regarding compatibility with memory integrity. Acronis is going to bleed customers like crazy, and as soon as I have a minute to research alternatives that will include me (and the dozens of clients I support) whose systems I have been installing Acronis software on for over a decade.
What a joke ...
Daniel Snooks wrote:Jose Pedro Magalhaes wrote:Lisa Cross wrote:Acronis is using this driver conflict to eliminate all our paid licenses in an effort to sell us on buying a subscription service.
Since I paid for a "Perpetual License", this is their way to attempt to force me into re-purchasing.
Perpetual = forever. Obviously, they have placed profit over customer loyalty.
I will NOT be purchasing additional products from a company that treats me that way.
Unless, of course, they reconsider and fix this one driver causing the issues "tib.sys" driver
Hello Lisa,
Thank you for your message. I have relayed it to our team.
I would like to inform you that Acronis True Image 2020 has reached its end of lifecycle since 2020. Therefore, any updates or support for this version have ceased several years ago.
I would also like to clarify that we are not attempting to sell you any product or impose anything on you. The memory integrity feature is not supported on outdated versions of our product.
To address your concern, I recommend referring to our knowledge base article at https://kb.acronis.com/content/70782 and following the suggestions provided there.
Thank you for understanding.
I just read through this entire thread. Jose, it appears that you didn't even bother doing that when you first responded on April 4th. This latest response to Lisa is complete garbage as well ... ATI 2020 did not reach it's end-of-lifecycle in 2020 (although it did in 2021 Acronis Support Lifecycle Policy for Consumer Products).
The fact that memory integrity is not supported in the 2020 version of ATI is part of the entire point of this thread, which you might have realized if you had bothered to even read. This thread was started in September of 2021 which means that technically support had ended the previous month, but issues with memory integrity go all the way back to the Windows 10 April 2018 Update when it was introduced ... and Acronis continued to release new versions of their product (including the 2020 version 16 months later) which did not address the issue, yet marketed them as being compatible with Windows.
It's total BS and reminds me of when Windows 10 was first released ... the version of ATI purchased the previous year was incompatible and the only options were to update to the new version (less than 12 months later) or stay on Windows 7). I was pissed about that, but it pales in comparison to this current insanity regarding compatibility with memory integrity. Acronis is going to bleed customers like crazy, and as soon as I have a minute to research alternatives that will include me (and the dozens of clients I support) whose systems I have been installing Acronis software on for over a decade.
What a joke ...
Hello!
Thanks for your feedback and please accept our apologies for the inconvenience.
We passed the message to the team.
Thanks in advance!
Upgrade from Windows 10 to Windows 11 failed with BSOD (ATI 2021 installed and working so far).
Reason was tib.sys.
Next I renamed this file. Upgrade succeeded.
Now ATI 2012 still works. But mounting a .tibx image fails:
- using a standard user account just nothing happens
- using an administrator account after selecting the desired partition an error message appears stating that a drive letter could be assigned to a partition
How can I repair this error?
Andre, welcome to these public User Forums.
TIB.SYS is not used for Mounting, Validating or opening backup archive images in Explorer.
It is used only by the Try & Decide feature, so renaming that tib.sys file should not affect those functions.
I have ATI 2021 installed on my own Windows 11 system with Core Isolation enabled and with tib.sys renamed and the Windows shell integration to give Mount etc is working fine.
I would suggest that you do the following:
First, turn off Core Isolation and restart the computer.
Next, perform a Repair install of ATI 2021 to ensure that Acronis Windows shell integration is repaired.
Check that the Mount feature is working again.
Rename tib.sys to tib.~sys then restart the computer.
Re-enable Core Isolation.
I have a laptop where I had renamed the tib.sys file to bypass the Memory Integrity issue. The fix worked flawlessly until upgrading the laptop to Windows 11 a few weeks ago. Now memory integrity cannot be turned on, but it does not identify any offending drivers (a couple of others in this thread have had the same problem). Does anyone have a suggestion of how to get this to work now? I tried the one suggestion noted in this thread but that did not work for me.
Paul
Paul Hussey wrote:I have a laptop where I had renamed the tib.sys file to bypass the Memory Integrity issue. The fix worked flawlessly until upgrading the laptop to Windows 11 a few weeks ago. Now memory integrity cannot be turned on, but it does not identify any offending drivers (a couple of others in this thread have had the same problem). Does anyone have a suggestion of how to get this to work now? I tried the one suggestion noted in this thread but that did not work for me.
Paul
Hello Paul.
Please refer to the following KB and apply the solutions: https://kb.acronis.com/content/70782
Feel free to update the thread if you have any questions.
Thanks in advance!
Hi Jose. The only "solution" listed in your recommended KB is to disable memory integrity. I don't want to do that. I have a desktop running windows 11 where renaming the tib.sys driver to tib.~sys solves the problem. Yet I also have a laptop running windows 11 where that fix does not work. How can I get my laptop to work like my desktop? I am running Acronis True Image 2018. Does the renaming fix somehow no longer work?
Paul
Paul Hussey wrote:Hi Jose. The only "solution" listed in your recommended KB is to disable memory integrity. I don't want to do that. I have a desktop running windows 11 where renaming the tib.sys driver to tib.~sys solves the problem. Yet I also have a laptop running windows 11 where that fix does not work. How can I get my laptop to work like my desktop? I am running Acronis True Image 2018. Does the renaming fix somehow no longer work?
Paul
Hello Paul. That's an expected behavior. Acronis True Image 2018 is a legacy version and has not been supported or updated since 2019: https://www.acronis.com/en-us/support/lifecycle/consumer/#true-image. Please also note that W11 is not supported for Acronis True Image 2018: https://www.acronis.com/en-us/support/documentation/ATI2018/index.html#40808.html. Thanks in advance!
I'm following the workaround and agree that Acronis should have had a disable feature for try and decide none of us seem to be using anyway. You're the man Steve Smith!
I'm also disappointed there is no more supported perpetual option and only subscription. Subscriptions are too expensive over a 3 year in life in comparison.
What other products are you using in place of Acronis that are comparable for a similar price? I don't want cloud trickle sync backups. I only do local external drive backups with 256 encryption and take by backup drives offsite locked up.
Jeffrey, welcome to these public User Forums.
You can continue using your perpetual licensed version of Acronis True Image such as 2021 (or most recent earlier versions - 2017, 2018, 2019, 2020). These may not be eligible for support from Acronis but they work just fine with both Windows 10 and 11.
In terms of other products, see forum topic: Reflecting on a Post-ATI World where there is lots of discussion on alternative products. I also use Macrium Reflect 8 but they too have decided to go down the subscription route so I am just keeping my perpetual licenced products there too!
I performed the tib rename workaround here and that cleared Acronis from the incompatible list, but core isolation still wouldn’t turn on after reboot/service restart.
Big warning here, there are Microsoft forum posts with registry changes to Defender to fix it not turning on. That went horrible for me and it changed so many other registry settings it was more worth the time to rebuild. Backout of the dword changes and recovery points didnt resolve the issue. I had to format and reinstall. Issues seen were app windows opening but blank, high runtime on cpu, and cpu in red but below threshold in tash manager.
in reinstalled the last True Image 2021 build and core isolation is fine so far. Ill post if that changes