search

abbodi1406 / KMS_VL_ALL_AIO

Smart Activation Script
GNU General Public License v3.0
8.12k stars 1.08k forks source link

Stuck and Error #27

Closed SeriousHoax closed 2 years ago

SeriousHoax commented 2 years ago

When I try to activate MS Office 2021 LTSC it gets stuck like the screenshot below: 1 After waiting for a few minutes, this appears: 2 No Antivirus is interfering with it I can confirm. My AV was also turned off and I tried this with two AV products. So that's not the issue. The "SppExtComObjHook.dll" was not present in System32 as stated in the second screenshot.

To make the activation successful, I had to download the "SppExtComObjHook.dll" file from online, paste it into the System32 folder when it got stuck like the first screenshot. And then office got activated and the SppExtComObjHook.dll file was auto deleted after the process. 3 My system is Windows 11 Enterprise latest build 22000.613.

mrambossek commented 2 years ago

That is exactly the file that AV is unhappy about. Try using Add-MpPreference -ExclusionPath "C:\install" in a powershell, then put the aio zip into that directory and only unpack it there. That way defender should leave it alone. 6cpmle

SeriousHoax commented 2 years ago

That is exactly the file that AV is unhappy about. Try using Add-MpPreference -ExclusionPath "C:\install" in a powershell, then put the aio zip into that directory and only unpack it there. That way defender should leave it alone.

The file is not detected by any AV at the moment: https://www.virustotal.com/gui/file/29ae6f149e581f8dbdc01eed2d5d20b82b597c4b4c7e102cab6d012b168df4d8 Also, as I said, I turned off Microsoft Defender before running the script. It didn't block anything. MS Defender on or off doesn't make any difference. I also tried it with another AV installed, which is Bitdefender. Bitdefender was also turned off. So looks like the error is not related to AV.

Technetium1 commented 2 years ago

Whether or not you have another AV installed, Defender WILL run alongside unless explicitly disabled separately. You must also reboot before it actually disables.

SeriousHoax commented 2 years ago

Whether or not you have another AV installed, Defender WILL run alongside unless explicitly disabled separately. You must also reboot before it actually disables.

That is not correct. Defender automatically disables itself when a third party AV is installed (Those which integrates into Windows Security as the real-time AV). It's possible to keep Defender as a Periodic scanner without real-time protection, but that feature is off by default. Today I tried the tool with another AV ESET installed, and the result is the same. ESET detects the AIO, but it was added into exclusion as well as the real-time protection was off. Also, this is not the first time I'm using abbodi1406's KMS_VL_ALL_AIO, I used it in the past with no issue.

abbodi1406 commented 2 years ago

Do you have C:\Windows\Temp folder?

SeriousHoax commented 2 years ago

Do you have C:\Windows\Temp folder?

Hi! Yes, I do. It asks for admin privileges to enter the directory and after that I can enter. image z

abbodi1406 commented 2 years ago

Did you try to reboot and run again? does v45 works? could you enable debug mode and share the log?

you can always use the traditional version (no embedded files, but no menu either) https://pastebin.com/cpdmr6HZ

SeriousHoax commented 2 years ago

Did you try to reboot and run again? does v45 works? could you enable debug mode and share the log?

you can always use the traditional version (no embedded files, but no menu either) https://pastebin.com/cpdmr6HZ

Thanks. The traditional version works without any issue. This is version 45: 45r Version 45 is very quick to say it can't be converted and also writes the log superfast. While version 46 takes a long time to write the debug log. Debug log 46: https://send.vis.ee/download/a8b31c21aaa13806/#QkmenORDd_4TQMmRrq6gTA

abbodi1406 commented 2 years ago

Do you have Device Guard or AppLocker enabled? something or some group policy is locking Powershell into Constrained Language Mode, which prevent the execution of dll extraction

SeriousHoax commented 2 years ago

Do you have Device Guard or AppLocker enabled? something or some group policy is locking Powershell into Constrained Language Mode, which prevent the execution of dll extraction

Oh! I did that a couple of months ago. I set Powershell to Constrained Language Mode for security reason. It didn't come to my mind that it could be the reason of this issue. I'll either disable that or use the traditional activator in the future. Sorry for the trouble. You may close the issue now.

abbodi1406 commented 2 years ago

I also didn't about that restriction before. Thanks for feedback.