Chm files wont open

I didn't realize MS thinks they are executable files unblock is reserved for those that are executable. No matter if I browse the LAN to the files or on the server directly, no go. Just now had to deal with this issue. Like robertchown found, unblocking wasn't enough. To continue this discussion, please ask a new question. Spiceworks Help Desk. The help desk software for IT. I double checked the registry and the Local Intranet zone in IE and everything looks like it should.

Known issue. The CHM issue is a casualty of a security hardening change in previous updates. Retest with monthly currently scheduled to release in the September Preview that will go mainstream the 2nd week of October How are you launching the chm files from IE Have you tried their support forums? The process that is running when I launch it is hh. CHM file is located on a network share on a file server. We use a DFS namespace for this fileshare and using group policy, we map a network drive to everyone's desktop.

I'm sure that it would work if I saved it locally because the CHM's still work fine when run from the local machine. Unfortunately we have some legacy files that a lot of users need to access, and having to copy the CHM files to their local machine every time is a giant pain in the rear. These are very old help files and I don't know if the company exists anymore or could help us.

I wonder if the problem that I am having is an unintended side effect of their update, or if it was done to close a security hole. We are having this same issue since updates this weekend. We too have this issue after the KB was installed. Remote execution of a CHM no longer works nor does the registry modification to allow this as in past times. This affects all CHM files to my knowledge. CHM" to a network location and then double click on it.

The content pane on the right will be blank. I can confirm that this issue exists and I have been unable to find a workaround that doesn't involve copying the.

I confirm also that this issue exists and that there is no workaround that doesn't involve copying the. I have the same problem since I switched to version For me, your solution is not an option, because.

We also open CHM Files from a share in our applications on thousands of clients. We are not able to force our customers to install everything local. Please Microsoft, fix this and continue using the existing registrykeys or at least give us another possibility to white-list UNC paths.

Please warn users when recommending to revert security patches. What CVE will users be vulnerable for when applying your "solution"!? This workaround does work, but due to the number of users we'd have to deploy it to, and how infrequently they access CHM files, I have decided to wait before implementing it. Our users have gotten used to copying them local when they need to.

Although I haven't tested it, I would think deploying it via group policy would not be very difficult. I have only received feedback from Microsoft that the problem is known and a solution is being worked on. Long speech, the mistake still exists. For the transition solution described here, system files are exchanged, you! You can solve this problem by copying the following files from unpatched systems before the May update to the corresponding System32 folders.

For x64 systems, for 32 bit programs from which help e. I'm glad to see this forum topic. I've been having this issue on our network also. Although there isn't a complete answer, it's identified what the problem is, and I appreciate it.

So I'll be able to do this on any PC that needs help access, and hope that the issue is resolved in the July update. They have recommended the mklink solution, which does not help us. That would require changing programs to point to the local directory.

If you open the CHM file from a network drive, it is displayed as shown in the screenshot. The solution is simple: copy the CHM file to your local hard drive and open it from there. The CHM file should now work. In order to be able to use CHM files from the network, an intervention in the registry is necessary.

The problem may also occur if the CHM file was downloaded from the Internet. This character can not be used as well as "? All those have special meaning. Try to remove all hashes and other special characters from the file and directory name.

That is why Windows security updates may block its content. Your CHM file may be located on a network computer, network drive, that exists in a restricted zone.