how can i fix error code 2147500037

Anonymous
2013-04-25T03:09:27+00:00

Original Title:

Network Programs Network Networking Internet Website Web Site URL Web Site

how can i fix error code 2147500037

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

188 answers

Sort by: Newest
  1. Anonymous
    2016-07-13T23:44:45+00:00

    I did a screen print, and copied it to a text document, and printed it that way.  I agree with Bigpapa, MS is still trying to shove IE down people's throats.  Shivam is just toeing the company line.

    Thanks for help. It kept saving it to OneDrive tho. But then I did the Ctrl-v on Word and it copied it there, then printed and saved. I couldn't print from OneDrive, the print and cancel option were grayed out. When I changed the browser default to IE, that didn't help, even when I changed all to windows default and then restarted my computer.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-07-03T09:25:35+00:00

    This is an absurd answer, you have got the details, almost 100 people has the same error, code only when trying to pront the password and instruction to share folders in their network, why is MS always doing as the errors are human related, fix it in god's name and spare dum answers, read the posts.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-18T01:23:27+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2016-05-17T23:59:27+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2016-05-14T19:43:19+00:00

    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.

    Was this answer helpful?

    0 comments No comments