MCCD ✭

Unfortunately that seems not to be the case; @Alexandru_BD may I get the subscription extension please?

It's nice that OP got a validity extension, too bad everyone else in this thread that submitted logs/screenshots or had tickets on this bug - didn't.

Eagerly waiting for the .199 build…

It should but it doesn't finish in over an hour - even with the latest kit - so it's safe to assume it's stuck.

@Flexx Thank you for your reply. That was what I've thought it meant, although it was a different file at every failed update. After it errored , I've rebooted, then forced uninstall with Bitdefender_2023_Uninstall_Tool, twice. Downloaded the latest install kit from the BD Central and right after the ending of the install…

Excerpts from the freshest self-update C:\Program Files\Bitdefender\Bitdefender Security\installer\fullinst.out1 -Fullinstall: added to files: [C:\Program Files\Bitdefender\Bitdefender Security App\about.exe] -Fullinstall: added to files: [C:\Program Files\Bitdefender\Bitdefender Security\accessl.dll] -Fullinstall: added…

Today's 84% failed update brought once again by wslib: wslib installing file C:\Program Files\Bitdefender\Bitdefender Security App\wscfix_app.dll wslib failed to install file C:\Program Files\Bitdefender\Bitdefender Security\accessl.dll, step: 21, error: 13 wslib install error -2011 (Install has failed (maybe because files…

To be fair, for the first time their suggestions worked because there were apparently some NTFS issues - but why does it appeared again? This time there seem to be no filesystem issues... Checking fs locks with procmon and other Sysinternals tools doesn't show anything meaningful.

So , again, me too stuck @84% after a week of working updates. Tried to uninstall … stuck; reboot; used Bitdefender_2023_Uninstall_Tool.exe twice; chkdsk c: /f /r ; Install again. … aaaand stuck at 84% forever - maybe because: (excerpts from fullinst.out1:) wslib failed to install file C:\WINDOWS\system32\drivers\atc.sys,…