A small number of dmg files on Mac fail to open, and the problem cannot be found. I don't know if it is a bug or something else. Please give me some advice.

Replies

• Anonymous534 May 12, 2025
  There seems to be a discussion here: https://forums.macrumors.com/threads/diskimagemounter-cant-be-opened-36. 2023648/ According to this discussion, it should be a bug in a certain version. You can open the Disk Utility first and then open the dmg file. If this is really the case, it is better to upgrade the system
• Poster May 12, 2025
  @ Anonymous534 # 1 Mainly, I now have the latest macos15.4. 1. I've been checking all night and I can't find the result
• Anonymous1436 May 12, 2025
  Restart Resolution
• Poster May 13, 2025
  @ Anonymous1436 # 3 Restarting can't solve the problem. It has been restarted several times
• Poster May 13, 2025
  New problem: I found that some png images have this problem too, the app "PictureView.app" won't open. -36. Is it a hard disk or system problem?
• Anonymous114 May 13, 2025
  Is it a file permission problem? I remember that onyx program has a cleaning and repair function. You can try it
• Anonymous2105 May 13, 2025
  @ Anonymous2106 errors Most of them are problems with files or storage devices. Your reproduced dmg problem, it seems that the file is not broken. I used to have a dmg generated by a lower version system many years ago that could not be opened in a new system, and then it was opened on a lower version system.
• Poster May 13, 2025
  @ Anonymous114 # 6 I just updated the MacOS15.5 system today. I'm going to go home and upgrade the system and try to see if there are any problems. Try this onyx again
• Poster May 13, 2025
  @ Anonymous2105 # 7 I just updated the MacOS15.5 system today. I'm going home and upgrading the system to see if there are any problems. I'm puzzled
• Poster May 13, 2025
  I tried reinstalling the system and there is still a problem. Do I have to erase all the data and reinstall it? (┬ _ ┬)
• Poster May 14, 2025
  Sudo xattr-r-d com.apple.quarantine solved it at once, magical
• Anonymous2107 May 16, 2025
  Finally encountered the same problem. I just bought a Mac mini in Guobu a few days ago, and it was still installed normally a few days after activation. Then I found that any. dmg could not be opened normally, and the prompt was exactly the same as what you said. "The application" DiskImageMounter.app "could not be opened.-36", I found a bunch of answers on the Internet, but they were all wrong and could not solve the problem, and then I really solved it following the poster's post. to talk briefly, my understanding is: macOS installer `. dmg ` is essentially an image. Double-click to install actually mounts the image through the ` DiskImageMounter.app ` that comes with macOS and then installs it. Double-click the image to mount The image is essentially the same as executing ` hdiutil attach/path/to/xxx.dmg ` in terms of realizing the purpose, which is to mount the image and then start the installation. Now it is reported that the application "DiskImageMounter.app" cannot be opened-36 "`. In fact, it is because the extension properties of the `. dmg ` file have been changed accidentally or incorrectly. My understanding is that it is probably similar to the `. exe ` file on Windows. It was originally defined as an application installation package in Windows, but now it has been changed due to some problem. The Windows application installer cannot recognize the `. exe ` file as an application installation package, so it cannot be installed. (I don't guarantee this 100%. I also understand it according to my ideas and Gemini's explanation) The original default extension property of the `. dmg ` file was the application installation package, but now it is changed to something else by mistake, ` DiskImageMounter.app ` cannot mount `. dmg ` as an application installation package. I recalled it, probably because I installed the compression software ` Keka `, and then the extended attribute of `. dmg ` was changed when associating the format, because I really couldn't think of other possibilities. Back to the original poster's solution, in fact, after I entered ` sudo xattr-r-d com.apple.quarantine ` at the beginning, my problem was not solved. After execution, the terminal reported an error: ` Not enough arguments for option-d. Expected at least 2 but got 1 `. The reason is that the ` xattr-d ` command is used to delete the extended attributes of the file. Its basic usage is xattr-d < attribute name > < file path >. The command I entered ` sudo xattr-r-d com.apple.quarantine ` only specifies the name of the attribute to be deleted ` com.apple.quarantine `, but it doesn't specify which file to delete this attribute from, so the system prompts that there are insufficient parameters. The correct command to remove the ` com.apple.quarantine ` attribute would be ` sudo xattr-d com.apple.quarantine/path/to/your/app-name.dmg `, where `/path/to/your/app-name.dmg ` needs to be replaced with the full path of the actual downloaded. dmg file. Then I searched for the attribute ` com.apple.quarantine `, which is part of the security mechanism of ` macOS Gatekeeper `, and it will mark files downloaded from the Internet. When a user opens an application with this attribute for the first time, the system will check (such as the developer's signature, whether it is notarized, etc.), and a warning may pop up, such as "the file is corrupted" or "the developer cannot be verified". Therefore, removing this attribute can solve the problem that this kind of security prompt causes the application to be unable to open. One more word, strictly speaking, it was the first time I used macOS (because the real first time was when I was in college when I tossed the black Apple 2333 on an HP machine). Everyone said that Windows had many problems, and Apple was very worry-free. For development, various environments and software installation, macOS is really, really easy to use. For my needs, it is very close and stronger than Linux, and because it has an easy-to-use GUI compared to Linux, I think the experience is very good. But on the other hand, if you encounter some system problems in the process of using macOS, such as this one, it may be because of the number of users, and there are really few related questions and answers that can be found. In contrast, although everyone is complaining about Windows, because there are enough users, the convenience of solving problems after encountering problems is much better than macOS. PS: Also, I don't feel the icon Finder at ordinary times, but it looks really aggressive when I encounter problems and report errors https://imgur.com/WRBU67d
• Poster May 16, 2025
  @ Anonymous2107 # 12 Haha, I was lazy. In fact, I omitted adding the dmg file after that command. In fact, I added it because this command is usually used to solve the problem that the app is displayed damaged when opened. I never thought of using it. on dmg file
• Poster May 16, 2025
  @ Anonymous2107 # 12 In addition, "I recalled it, probably because I installed the compression software ` Keka `, and then the extended attribute of `. dmg ` was changed when associating the format, because I really couldn't think of other possibilities." When you said this, I seem to have used maczip to open dmg once. I also deeply doubted this problem, but I tried changing the opening method to DiskImageMounter.app and it didn't work, so I didn't pay attention to this
• Anonymous2107 May 17, 2025
  @ Poster But I soon discovered a problem. Because this command is aimed at a certain installation package, the execution effect is only useful for a single package. I'm not sure if I want to delete extended properties for all. dmg operations. What should I do? After all, it's too troublesome to manually understand every installation
• Poster May 17, 2025
  @ Anonymous2107 # 15 I only have some dmg files with this problem, and most other dmg files don't have this problem, so it's fine
• Poster May 17, 2025
  Found the same problem https://discussionschinese.apple.com/thread/256055678? sortBy = rank