Announcing Windows 10 Insider Slow Build 17025 for PC Insider

Page 5 of 43 FirstFirst ... 3456715 ... LastLast

  1. Posts : 30,579
    Windows 10 (Pro and Insider Pro)
       #40

    Kari said:
    Not for me, I was offered 17017 whatever I did.
    Oh, forgot to mention running Resetreregister Windows Update (Another Brink's tool) couple of times before...
      My Computers


  2. Posts : 213
       #41

    I got this weird startup program after updating

    Announcing Windows 10 Insider Slow Build 17025 for PC-untitled.png

    Scanned with MBAM & Defender & ADWcleaner and got nothing. It's placed in a hidden folder in C:\. Any idea what this might be?
      My Computer


  3. Posts : 1,174
    Windows 1.00 to Windows 11 Pro 64-bit Build 22000.194
       #42

    Announcing Windows 10 Insider Slow Build 17025 for PC-screenshot-29-.png

    Just back from Belfast. Was ready to restart when I checked. Making ISO now.
      My Computer


  4. Posts : 213
       #43

    Also in the Windows Update tab the following text appears:

    *Some settings are managed by your organization
      My Computer


  5. Posts : 3,274
    Windows 10 and windows insider
       #44

    doubtingtom37 said:
    Hmmmm.. Will do.....
    THX!
    Were you successful with this?
      My Computer


  6. Posts : 31
    Win10 Pro 64 Build 16237
       #45

    magilla said:
    Try unplugging any usb devices that are plugged in—and SD cards.
    All unplugged except Logitech Illuminated (corded) keyboard and G400 mouse. Same issue as before. Went to Insider settings and backed out until next Release. All back to normal on 17017 now. Tried 'Fix me' and same problem again.
    Over time, each of the (3) desktop PC's has experienced one-or-more Pro Insider Update problems, while other (2) have not. Then seems to 'rotate' to another. ????? Perplexed that they run without issue, daily, then all Update, then random failure.
    Over time, all get Updated, then fine until one like this.
    Thank-you for suggestion. Maybe wait a day or so and try starting Pro Insider again ?
      My Computer


  7. Posts : 3,274
    Windows 10 and windows insider
       #46

    doubtingtom37 said:
    All unplugged except Logitech Illuminated (corded) keyboard and G400 mouse. Same issue as before. Went to Insider settings and backed out until next Release. All back to normal on 17017 now. Tried 'Fix me' and same problem again.
    Over time, each of the (3) desktop PC's has experienced one-or-more Pro Insider Update problems, while other (2) have not. Then seems to 'rotate' to another. ????? Perplexed that they run without issue, daily, then all Update, then random failure.
    Over time, all get Updated, then fine until one like this.
    Thank-you for suggestion. Maybe wait a day or so and try starting Pro Insider again ?
    The other suggestions is to copy from one of your 'successfully installed' machines the volsnap.sys file and paste it to the machine giving you problems. The directory to find is windows/system32/drivers/volsnap.sys. On your 'donor' machine you need to take control (see Brink's tutorial for this) of the file, and same for the 'recipient' machine. You can do this while the machine is still in 17017. Also note that the recommendation of Microsoft is turn off 'restore points' My issue was USB drives that were plugged in. When I unplugged them, the install took place, but replacing the USB drives caused a BSOD pointing to volsnap.sys. After I replaced the volsnap.sys with one from working directory, the problem went away. Now, I don't have this problem in 17025. Good luck.
      My Computer


  8. Posts : 477
    Win 10 Pro x64 19645 Fast
       #47

    Download, install and ISO went quickly and without issue. Now time to see what I have and how well it works.
      My Computers


  9. Posts : 31
    Win10 Pro 64 Build 16237
       #48

    magilla said:
    The other suggestions is to copy from one of your 'successfully installed' machines the volsnap.sys file and paste it to the machine giving you problems. The directory to find is windows/system32/drivers/volsnap.sys. On your 'donor' machine you need to take control (see Brink's tutorial for this) of the file, and same for the 'recipient' machine. You can do this while the machine is still in 17017. Also note that the recommendation of Microsoft is turn off 'restore points' My issue was USB drives that were plugged in. When I unplugged them, the install took place, but replacing the USB drives caused a BSOD pointing to volsnap.sys. After I replaced the volsnap.sys with one from working directory, the problem went away. Now, I don't have this problem in 17025. Good luck.
    Terrific help ! Thank-you so much.
    Will proceed and confirm ...
      My Computer


  10. Posts : 659
    10 preview 64bit
       #49

    Oh well things going backwards,
    got to 23% installing then swung straight back to prepairing.

    NO warnings or error messages

    View installed shows failed 0x8024200d
    0x8024200D -2145116147 WU_E_UH_NEEDANOTHERDOWNLOAD The update handler did not install the update because it needs to be downloaded again.

    bargain.


    Roy
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:41.
Find Us




Windows 10 Forums