I tried running the DISM command this evening, and I got an error message. I will provide screenshots.
- DISM command
- Current version of Microsoft Office
- Windows updates
- Current version of Norton
I look forward to your help.
Please review:
https://community.norton.com/t/ai-exe-bad-image-error-starting-ms-powerpoint/357404
message 27:
https://community.norton.com/t/ai-exe-bad-image-error-starting-ms-powerpoint/357404/27
========================================
https://windowsforum.com/threads/how-to-fix-aswhook-dll-errors-on-windows-a-simple-guide.350972/
Note: windowsforum.com has ads
https://windowsreport.com/aswhook-dll/
Note: windowsreport.com has ads
1 Like
Thank you for taking the time and effort to respond.
I had seen both of those references prior to creating my post. Please allow me to elaborate.
The first post about “PowerPoint,” though interesting, differs slightly from my issue. I use use primarily Word and Excel, and so far they seem unaffected. So I tried PowerPoint last night. The program opens fine and it is able to open files fine. I have not had any issues with Office so far.
Every few weeks, I tend to use the following commands using an elevated prompt with administrator privileges as part of my good computing practices:
- DISM.exe /Online /Cleanup-image /Restorehealth followed by
- sfc /scannow
Normally, I buzz through those two commands with no issues. Yesterday, however, they caused some grief. That is why I posted with the different screenshots.
I wanted to accomplish the following objectives:
- Let Norton know that there is an issue with DISM
- Even though Office seems to be running fine, let Norton know which version of Office I am running (it’s the current beta version)
- Let Norton know that just prior to running DISM, Windows 11 (Insider Preview) updated itself
- Provide the Norton version number
Regarding Windows Forum, it suggests five different solutions:
- Update Microsoft Office, I double checked and my version is fully updated
- Repair Office: Because Office is not giving me any grief, I am not inclined to use Quick or Online Repair
- There is no “affected app” to reinstall; I cannot reinstall “DISM”
- Rollback Windows Update is a possibility, though the only issue so far is DISM spits up an error message
- Uninstall Norton is always a possibility of I start encountering real grief
As mentioned, it is only because I ran DISM as part of my housekeeping that I noticed there is an error. Otherwise, I would be oblivious to it. I am hoping that Norton fixes its issues. If push comes to shove, I will uninstall Norton.
I hope this added detail helps Norton as it addresses its aswhook.dll problem.
If I were encountering this problem, I would first uninstall Norton completely since aswhook.dll is associated with Norton (Avast), not Windows. Then run the DISM command. If that doesn’t generate an error message, it confirms that there’s either a compatibility issue between the dll and Win11 or the dll file got corrupted when Norton installed or updated. I’m leaning toward file corruption since I’ve encountered unrelated corruptions recently when Norton installed or re-installed, It even deleted an unrelated app on one of my computers.
If your DISM command produces no error message, do a clean install of Norton and check again. If you see the error again, then it’s a compatibility issue. If you’re not encountering problems using MS365, one option is just wait and see. Hopefully either Norton or MS will fix it in a future update. Also possible that it’s already fixed in Windows 11 version 24H2.
aswhook.dll is an essential component of Avast Free Antivirus. It is responsible for hooking certain system calls and redirecting them to Avast’s own modules for real-time protection. Without this file, Avast may not function correctly.
So far, I have not encountered problems while using Microsoft 365, so I am planning to “just wait and see.” If I do run into problems, then I will follow your suggestions by uninstalling Norton. Like you suggested, though, I am hoping that an upgrade along the way, either by Norton or Microsoft, will address the issue.
Regarding the operating system, I am on the Windows 11 Insider Preview Build. I don’t plan on rolling that back.
Thank you for your response.
Chances are the error is caused by a compatibility issue but as the error message notes, the dll file “may contain an error.” I take it to mean that it’s possible the file is corrupted. Since aswhook.dll is an “essential component” for Norton to function correctly, it might be good to err on the side of caution and remove/reinstall Norton. If the file is corrupted, that should fix it. Then again, I tend to be cautious when it comes to cybersecurity so this may be unnecessary.
Sure, I will go ahead and make changes. My process will be as follows:
- Uninstall Norton 360
- Reboot and try DSIM
- Install Norton 360
- try DISM
Let’s see what happens.
Okay, I did the following:
- Uninstalled Norton 360 using this page: Download and run the Norton Remove and Reinstall tool for Windows
- Restarted and tried DISM (passed with flying colors)
- Installed Norton 360
- Restarted
- tried DISM and failed (see screenshot)
The key takeaway is that many people likely have an issue that they do not know about because they never use DISM.
Can someone, please, flag this thread to the Norton?
1 Like
Based on the info in your screenshot, you installed a new release of Win11 Insider Preview (IP) on Feb 1. Since you routinely run DISM and didn’t run into this error before, the newest version of Win11 Insider Preview is most likely the source of the incompatibility. You can send a feedback to Norton through the app. Go to Settings and under the About tab, you’ll find the Feedback button for reporting bugs and suggestions. That’s likely the best way to give Norton the heads up on this issue. I see that MS Insider Program has it’s own feedback link where you can report this bug. Provide feedback as a Windows Insider
The good news is the dll file isn’t corrupt. Since you haven’t encountered any problems in the performance of either N360 or MS365, seems like you’re good to go other than wait for either MS or Norton to address this issue.
1 Like
Thank you for your patience as well as your courteous and helpful replies.
I have done as you suggested by providing feedback to both Norton and Microsoft.
So now, I just wait.
1 Like
At least you know you’re not alone. It is frustrating, isn’t it.
I hope that Norton resolves this issue sooner rather than later.
1 Like
Indeed. I suspect Nortan/Avast will eventually recompile the DLL or Microsoft will correct it on their end. In either case it doesn’t seem to prevent DISM from finishing. It’s just a minor annoyance at this point so I’ll live with it.
I discovered running the command through powershell (terminal) instead of CMD works fine.
1 Like
All: The issue is fairly simple. Norton states they do not support Insider Builds on Windows as they are considered BETA. Although in the past I have ran Norton products on at least one of my rack servers with Windows 2003 and Windows Server Essentials 2016 without issues though they aren’t BETA OS’s.
SA
I see @SoulAsylum posted ahead of me.
That they don’t support Insider Builds is all well and good. The reality is that it doesn’t work, and our flagging this issue should be considered helpful. They can get head start in addressing this issue. And perhaps, they can change their methodology so that, regardless of future Windows builds, aswhook.dll never causes grief again.
Would you rather us not report this issue?
1 Like
Thanks for reporting it, it is indeed helpful. Norton has a team working on it for the product to support Windows 11 new releases that are mainstream updates outside of the Insider Program. The issue isn’t a new one and has been escalated to Norton for action previously. We Guru’s aren’t privy to when a new release may or may not address the issue since we do not work for Norton.
SA
2 Likes
I’m having this same error. I’m running Windows 11 24H2. When I try to create Veeam Recovery Media which uses DISM. I uninstall Norton 360. I’m able to create Veeam Recovery Media with no errors.
1 Like
Are there any news on this issue ->Veeam Recovery Media Creator and those DISM-Errors → ? Got it as well but using avast premium security, which is driven by the same engine as far as I know. Avast Support be like no one home. Only standard phrases, like reinstall a thousand times. Only hints givenare the ones i tried prior even googleing that behaviour. like sfc / dism cmds and related for powershell. but nothing.
@Technogod99 did you try doomclicking “ok” on the error message until veeam recovery media creator carries on with next step after adding drivers? I did, and the media has been created while veeam itself stated media successfully created. no error whatsoever. maybe ill try a recovery with this media, just to confirm all is fine. maybe after restore avast will not work properly on restored system and t h e n has to be reinstalled, i dare to predict.
Uhm I forgot: 1st I asked Copilot for a Solution and it made me aware to update to latest visual c++: “Microsoft Visual C++ 2015-2022 Redistributable (x64) - 14.42.34438”
Maybe useful, maybe not… 