Announcing Windows 10 Insider Preview Build 14291 for PC and Mobile Insider

Page 17 of 36 FirstFirst ... 7151617181927 ... LastLast

  1. Posts : 3,367
    W10 Pro x64/W7 Ultimate x64 dual boot main - W11 Triple Boot Pending
       #160

    Ztruker said:
    I think I figured out my problem.

    I did a clean install of one of the insider preview releases, don't remember which one, but I think I also deleted then created a new Windows 10 Pro X64 Oracle VM to do the clean install to. Hardware emulation was the same and the computer name is the same but I don't think activation liked it for some reason and I didn't notice it then.

    Now, looking at the devices registered to my MS account, I see a Oracle VM for 14257 and now 14291.

    I did a rollback to the previous Win 10 which ended up as 14279 and I don't see that one registered to my MS Account.

    Any idea how I can recover from this or do I have to install a qualifying Windows 7, 8 or 8.1 first then upgrade to the latest insider preview?
    Want to know how I fixed the bugs that suddenly came up with the Threshold 2 update last month? You can use the same method of downloading the TH2 updated to fix since apparently from the 10586.73 to 168 patched for not being able to rename files and folders! Everywhere even on the MSDN and TechNet sites no one had a working solution. So I simply enabled the Get insider builds option and allowed one of the latest builds to upgrade over being the 14267 I believe the latest at the time right before the 14271 arrived.

    All you have to do is see the Tech Bench latest download if not opting to use the MC tool to download and save the updated TH2 build and wait for the next build to arrive before enabling the Get insider builds! You don't have to go back to 7, 8,. or 8.1 once 10 has been activated on the present hardwares but simply slap a fresh install of 10 on once 10 has been activated the first time. The MS activation servers will know 10 was on and you will likely find the next install already activated by the time you reach the desktop the first time.
      My Computers


  2. Posts : 17,838
    Windows 10
       #161

    Clean install done.
    Snipping Tool and others still crash.

    This is new on a clean install:

    Announcing Windows 10 Insider Preview Build 14291 for PC and Mobile-1.jpg
      My Computer


  3. Posts : 3,367
    W10 Pro x64/W7 Ultimate x64 dual boot main - W11 Triple Boot Pending
       #162

    Edwin said:
    Clean install done.
    Snipping Tool and others still crash.

    This is new on a clean install:

    Announcing Windows 10 Insider Preview Build 14291 for PC and Mobile-1.jpg
    Why is it everyone else is having problems with this build? I have upgraded VMs as well as two desktops and still have a couple more VMs I could update to this build and so far everything works! I never have problems with the snipping tool going back to Vista! I suspect if you are using esd to iso or wim files to see the media made up for clean installs rather then continuing in progressive upgrades by the WU from the TH2 this is where something isn't going on fully!

    These latest builds seem to be geared to be installed as updates only. Since you won't be seeing service packs as you did in years past the newer builds are being geared for upgrade by update only which is the MS end goal. I would try simply slapping the TH2 on and then allow that to update to this one.
      My Computers


  4. Posts : 17,838
    Windows 10
       #163

    @Night Hawk :
    Beats me! I just walked away from my upgrade install of 14291 and did this clean install; same results on both sides!
      My Computer


  5. Posts : 3,367
    W10 Pro x64/W7 Ultimate x64 dual boot main - W11 Triple Boot Pending
       #164

    That's a weird one alright but suggests something else is needed. Here after several updates and now onto the second build's 7 side 10 VMs there not one has run into this. The screens posted earlier are the before and after on the main here.

    Here the 14271 build is still on the 7 side's VM on the second machine. I didn't get quite around to creating a new VM on Hyper-V on the 10 side since I won't be able to use the WS 12 Player there. And the 14291 is found simply waiting to go on as expected! In 58min. I'll then reboot into the 10 side and set up the new VM there on Hyper-V and allow that to update to this build as well.

    You may have to review what you have on for av and other types of system protections which can be a problem at times. Something has to be clashing somewhere since I should have run into something buggy on at least one of the upgrades. This is one reason for having several 10 VMs as well as the two builds all seeing the same thing.
      My Computers


  6. Posts : 963
    dual boot W10 10586th2/14291 rs1 Win. Insider since Jan. 2015
       #165

    post deleted by user
    Last edited by blutos cousin; 20 Mar 2016 at 05:05.
      My Computer


  7. Posts : 963
    dual boot W10 10586th2/14291 rs1 Win. Insider since Jan. 2015
       #166

    Night Hawk said:
    That's a weird one alright but suggests something else is needed. Here after several updates and now onto the second build's 7 side 10 VMs there not one has run into this. The screens posted earlier are the before and after on the main here.

    Here the 14271 build is still on the 7 side's VM on the second machine. I didn't get quite around to creating a new VM on Hyper-V on the 10 side since I won't be able to use the WS 12 Player there. And the 14291 is found simply waiting to go on as expected! In 58min. I'll then reboot into the 10 side and set up the new VM there on Hyper-V and allow that to update to this build as well.

    You may have to review what you have on for av and other types of system protections which can be a problem at times. Something has to be clashing somewhere since I should have run into something buggy on at least one of the upgrades. This is one reason for having several 10 VMs as well as the two builds all seeing the same thing.

    My Windows Snip tool is crashing now after working fine for a while and I use the recommended windows defender and mbam web protection on a metal 19241 install so it would be a simple thing to uninstall that and edit the reg for any scraps of it but I doubt that's the problem it's maybe some errant or incompatible code (on some configurations ) or f** up dll's somewhere.
      My Computer


  8. Posts : 17,838
    Windows 10
       #167

    Eliminating secondary monitors eliminated the crashing snipping tools issue, but, that's not acceptable!
      My Computer


  9. Posts : 22,740
    Windows 10 Home x64
       #168

    It is really odd.. this build like the last one works just fine for me. The only "issue" I did encounter was the taskbar clock I use really got messed up but that's not an issue.

    It could be that I have a very basic PC set up. Not really sure. Still odd.. and I got a message from MS for feedback on this build if it was causing me crashes or not.
      My Computer


  10. Posts : 963
    dual boot W10 10586th2/14291 rs1 Win. Insider since Jan. 2015
       #169

    Edwin said:
    Eliminating secondary monitors eliminated the crashing snipping tools issue, but, that's not acceptable!
    Right that's a bummer :
    That's interesting I have a 4K Sony HDR TV connected to my d/GPU as a second (extended desktop ) screen on an HDMI cable ofc.
    The TV been on when Snip tool been crashing but not on the PC input but more than likely the EDID stuff been going on anyway because I've been changing some of the TV HDMI inputs and Android TV apps and OTA with the remote .
      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 15:03.
Find Us




Windows 10 Forums