Same on my page.

It works if in IE11's developer tools (F12) you set User Agent string as "IE10".
-Open link (http://gmaps-samples.googlecode.com/svn/trunk/scrollzoom/scrollzoom.htm)
-Attempt to zoom in/out with scroll wheel (doesn't work).
-Open developer tools (F12)
-Switch to "Emulation tab"
-Change User Agent string as "IE10" (page refreshes)
-Attempt to zoom in/out with scroll wheel (works).

The issue is the same at https://google-developers.appspot.com/maps/documentation/javascript/examples/full/map-simple

 Issue 6071  has been merged into this issue.

(No comment was entered for this change.)

Same thing is happening to us as well.

 Issue 6151  has been merged into this issue.

This issue is also affecting us. This needs resolving urgently!

when will this be fixed? IE11 is being widely pushed now with the win 8.1 free update

Its not working in IE11 on Win 7 as well.

Any fix? The same problem here, I have page for my client, and it must works fine, but still no any fix.

Same question from my side. Is there a plan or a date when this issue might get fixed ?

Same thing is happening to us as well.

I'm running into the same problem. Is there a date for the fix?

This is affecting us too. Is there an ETA for the fix?

At the company I work for we have the same problem.
Since we have an Enterprise account I opened a ticket with them and here below is what they had to say.

While I would expect such an answer from a small start-up, it seems weird and troubling that a colossus the size of Google can't spare a single engineer to maintain released (and paid for, at least in our case) major/key products like Google Maps.
I do hope they get their act together and soon.


---------------------

The reason for the delay in response is that the Engineering team has been focusing on a project right now and has had very little time to focus on fixing bugs. Having said that, we recognize that the impact of this issue is becoming higher every day (already 51 people stared in on the issue tracker) so we have raised the priority of this issue report to P1 and asked the Eng team to follow up, and I will update you once we have a response. 

Unfortunately there does not appear to be any known workaround for this at the moment, but hopefully this issue will be fixed soon enough, so there will be no need to try to develop one. 

I have added 
<meta http-equiv="X-UA-Compatible" content="IE=10" />
to the head of my page. This forces the IE11 to behave as an IE 10. 
It is just a workaround.

And a terrible one at that. Is Google angry that IE has been getting more standards compliant in versions 9, 10, and 11... and thus want to force users into old document modes?

Okay it's probably not malicious, but I don't understand why this works on maps.google.com but not on anything built with the API.

Thanks, that works fine!
To prevent undesired side-effects on older IE versions I would add some server-side code to only add (or change) that meta tag if the user agent is from IE 11 (contains "Trident/7.0; rv:11.0").
Some paranoid check cannot hurt.

@adam.kuffel Thank you for the quick fix. I tried it out, but it did not work. It only "works" if I manually set the IE11 (Edge) with the console to IE10. Is there anything I can try or need to take care of to make this quick fix work?

Update from enterprise support portal:

The fix for this issue has been implemented and is now code complete.

A new experimental version of the JavaScript API (3.16) will be rolled out soon and include this fix. Please let us know if you observe this issue using version 3.16.

For more details about the upcoming release, please see the "Retirement of the Google Maps Javascript API 3.13" announcement in the Support Portal.

Nice, I just can't wait to switch our production sites over to an "experimental" version of Google Maps... (sorry for the sarcasm, but, WTF Google!)

A small but important correction is required here.  The good news is that this fix will soon be published into the existing 3.15 experimental release.  This release is due to graduate to the Release version in the following weeks.

Any news?

Are you still seeing the issue on the experimental version of the API? If so, please provide a link to a demo.

We cant use experimental version of api on production. We must use stable version.

3.15 will become the release version next week.

(No comment was entered for this change.)

Thank you!