how can i fix error code 2147500037

I am getting this error code when I try to "print" my homegroup password and ONLY at that time.

Thanks ET

the message reads ;- your homepage password could not be printed. Error code 2147500037. thanks.

So here I am at the end of 2017 and I just did a reinstall of Windows 10 and I am having this exact same issue. So I changed the default browser from Microsofts own Edge to IE and then tried to print the new Home Group password again and I still get the same error code. Everything else prints just fine from any of the computers on my home group but not the HG password. I then did a reboot and still the same issue. Arrrrrrg, no time for this.

We need a "Like" option.  "Helpful" is good if there's actually a fix or work towards a fix but, since that's all we have I'll select it as both replies above are appropriate.

This is to all the Microsoft tech people and to all the other people who have provided WORKAROUNDS for this problem.

Example Problem:  Your car won't start and you find out you have a bad/dead battery but you have to go to work.

Workarounds:             Workaround #1:  Jump your battery from another battery/car.

                                     Workaround #2:  You walk to work.

                                     Workaround #3:  You ride a moped to work.

                                     Workaround #4:  You ride a bicycle to work.

                                     Workaround #5:  You call for a taxicab.

These are all WORKAROUNDS for the example above.  These WORKAROUNDS DO NOT FIX THE PROBLEM.  The FIX/SOLUTION to this example is to buy a new battery and MICROSOFT DOESN'T WANT TO BUY A NEW BATTERY.

This problem is not a Homegroup or a Printer problem.  The problem is the way Microsoft has programmed this one print job (AND ONLY THIS ONE PRINT JOB) to require IE to be the default browser.

There are no other print jobs/requests that require IE to be the default browser.

Microsoft refuses to acknowledge that this is a programming error and refuses to fix the problem.

I hope someone in Microsoft has enough technical knowledge to fix this problem and not provide any more workarounds.

I wonder how it would feel to any Microsoft personnel to sit there and have to stop what they are doing, click at least 5 different times to make IE the default browser, a couple more clicks to print the document, then, at least 5 more clicks to change the default browser from IE to the browser of their choosing.

Well done Microsoft.

This is how all big businesses operate.  Just look at the financial meltdown and how these companies treated the consumers.  These companies were bailed out from the US Government but the consumers were left holding the bag.  No one was ever arrested, tried or convicted of a crime.  Even one of these companies took the bail out money and paid their top executives bonuses.  This is greed(money).

This is just one simple persons' opinion. 

Well said! A beautiful summary/writeup of this thread.

And happy belated three year anniversary to this bug report!

Created by webepa2 on April 25, 2013, who originally posted just an error code.

Within days the community identified the exact problem, provided repro steps for microsoft, and workarounds for the affected users. We thought these workarounds were going to be temporary, but three years later we still see the same workarounds spammed in here and no "Hey it's fixed, guys! Run Windows Update." in sight...

Still not fixed on May 18, 2016

At this rate Microsoft will drop support for Homegroup before fixing (or even acknowledging) this minor bug. When's that going to be... 30 more years?

I preferred the old reliable domain based networks anyway. I still use WORKGROUP.

CMD → NET computer \"name_here" /ADD

But I'm not giving up on this thread. Even if the ignorant, lazy (non-existent?) Microsoft Homegroup-assigned employees don't even bother to acknowledge it. Also, we are never even supposed to print out passwords. Making this an almost completely useless feature... That also happens to be broken.

But how much effort would it take to fix? (Or remove!) A lot, I think. They'd probably have to dig up the source code from tape archives or even floppies. And the legacy code that once passed security audit... Well it doesn't anymore. Windows Update has new, higher standards. You can't push garbage-grade code through anymore. Homegroup, being unsafe, substandard code fails a lot of the auto validation checks nowadays and cannot be updated anymore without getting a major rewrite first.

I am following the general threads here and thought I would add my experiences. I have a W7 Home Premium desktop and a W8.1 that I bought in Australia. (US keyboard but that's OK) I am trying to set up a home network and have come into exactly the same problem with the error code 2147500037. I also hate IE and have used Firefox on everything for years. Still haven't worked out how to print to my HP printer though.

I also want to alert others to another cheeky MS download. I don't want to use a password of any kind to sign on to my computers that are used on a home network at HOME! A couple of months ago I found I was unable to enter my laptop because MS had downloaded a directive in one of their Optional Updates that now means I have to enter a password. Again - I know there is a work around by opening another account but it shouldn't be up to me to do a workaround. Who are you MS to direct me to use my computer as you think I should? You have given me software for me to download and that I trusted (secretly) that could be described as malicious. We abhor all malicious software so why did you MS do this? Your answer will be interesting.