Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Win 10 system updates & Home Server 2011 Launchpad RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    The most annoying thing happens whenever Microsoft provides a system update for Win 10. Upon the reboot, Home Server 2011 Launchpad will not login. Every time I get a major update, I have to uninstall the connector software, and reinstall it in order to have Home Server continue functioning. And, I have to make a change to the registry entry, "PendingFileRenameOperations" in order for the Connector software to install.

    Does anyone know if there is a better solution to this? I like my WHS 2011, it works fine, except for this glitch. I do not want to purchase the "Essentials" as I am on a limited income and cannot afford that. Any help would be much appreciated. 

    Jim Marcum

    Jim Marcum

    Tuesday, June 18, 2019 2:06 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thank you for your detail feedback. 

    Based on my experience, system general update (such as monthly update)should have no effect on Connector. System upgrade, such as upgrade from 1803 to 1809, or upgrade from Windows 8 to Windows 10, such system ugrade operation may need us to manually re-install connector.

    I will post your feedback to product team, also, you may post it via Windows 10 system built-in feedback hub app.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Jimmarcum Tuesday, July 2, 2019 1:51 PM
    Tuesday, July 2, 2019 8:09 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    As far as I know, connecting problem on windows 10 after system upgrading, Connector re-installation on client system is an effective way until now. 

    Customers on WSE forum also feedback similar problem recently. If possible, please provide detail information about your environment:
    1. Run “Winver” on both client and WHS, provide me the detail OS version and build number.
    2. If problem happens on OS upgrade, or general update installation? Please provide the detail build number before and after the upgrade, or update kb number.

    I will post such problem to product team after I had confirm this problem on my test environment. 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 19, 2019 2:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for your reply. I don't know if I have the exact information you need, but I will provide what I know. I did not have a problem with the update on 6/12/19, but the one previous on 5/15/19 and many previous ones caused the Launchpad issue. My build number on the client is: Ver 1809 (Build 17763.667, but I am guessing you would want the build just previous to this last update which I do not have. The Update that caused the problem on the build of 5/15/19 was KB4494441.

    On WHS 2011, the Ver is 6.1 (Build 760.1 Pack 1. I hope this is helpful.

    Jim Marcum

    Jim Marcum

    Wednesday, June 19, 2019 1:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thank you for your detail information, I will try to reproduce it. And I will post it to product team once I successfully reproduced it on my VM.

    I am quite understanding the inconvenient it had brought to you, the connector re-installation can be used as temporary workaround. Also, thank you for your supporting for Microsoft products.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 20, 2019 2:43 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Don't Worry About That issue My Senior has Solved this.

    That Person Was my Head You Can Contact With This No. 8077750432

    Or You Can Visit any kind Of Development Services to Skydevelopers.net


    • Edited by amarsky9100 Thursday, June 20, 2019 9:58 AM Something Missing
    • Proposed as answer by amarsky9100 Thursday, June 20, 2019 9:58 AM
    Thursday, June 20, 2019 9:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
     

    Thank you for your reply. I received another reply from amarsky9100 that said his senior had solved this and I could contact him at 8077750432. I have no idea how to do that.

    Do you know what he is talking about or how to find this solution?

    Best,

    Jim Marcum


    Jim Marcum

    Thursday, June 20, 2019 12:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jim

    I suspect that amarsky9100 is a scam, so I would ignore it.

    I have a similar problem with WHS 2011, running on a Server 64 bit Win 10.  5 PC's/Laptops connected all running Win 10 OS, some 32 bit and some 64 bit.

    Recently 2 have stopped connecting.  Tried all the usual fixes without success. Hopefully Eve Wang can help.

    Steve

    Thursday, June 20, 2019 3:03 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Eve: Today I upgraded my HP Elite Laptop from build 1809 17763.557 to the new build 1903. I lost mt Launchpad again on this one. I am waiting for my HP Envy to finish the upgrade, but I assume it will fail again as well. On the Laptop I uninstalled the connector software and reinstalled it without problem. I will add my other machine when the update finishes.

    Thank you

    Jim Marcum

     

    Jim Marcum

    Friday, June 28, 2019 5:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I forgot the build for 1903. It is 18362.207

    Jim Marcum

    Friday, June 28, 2019 5:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Eve, I completed the upgrade from build 1809 to 1903 on my other two PCs, an Envy 700-230qe, and an HP Pavillion 9040. In all three cases, the update caused me to lose my connection to WHS 2011. I had to uninstall the connector in all three cases and reinstall it in order to continue using my backup server. And, except for the laptop, I had to use regedit to edit the registry to change the name for "PendingFileRenameOperations" by adding the number 2 in order for the install to go forward for the connector. While I can do this, it would be really neat if Microsoft could figure out why their new builds cause this problem with their own server system, even though I know they no longer support it. Thanks, for your efforts.

    Jim Marcum

     

    Jim Marcum

    Saturday, June 29, 2019 2:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thank you for your detail feedback. 

    Based on my experience, system general update (such as monthly update)should have no effect on Connector. System upgrade, such as upgrade from 1803 to 1809, or upgrade from Windows 8 to Windows 10, such system ugrade operation may need us to manually re-install connector.

    I will post your feedback to product team, also, you may post it via Windows 10 system built-in feedback hub app.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Jimmarcum Tuesday, July 2, 2019 1:51 PM
    Tuesday, July 2, 2019 8:09 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for your reply. I will keep watching regular updates within the same basic build to see if there are further problems with connector. Major upgrades such as 1809 to 1903 I can handle manually reinstalling connector as those upgrades are infrequent. If I continue to have problems with regular updates, I will report.  Enjoy your day!

    Jim Marcum

    Tuesday, July 2, 2019 1:51 PM