Windows 10: Windows 10 Threshold 2 (November Update) Installation Problems

In the end, I took out the memory again, and the whole update process completed.

Just in case anyone thinks this is a one-off event with faulty memory or similar, I have 10 of these laptops I have to deal with.

I am quite disturbed about the integrity of Windows 10 updates and the way they are installed.

 

Sounds like a Vista x64 problem for some reason since that's the last time I had heard of anyone needing to pull any ram out! That was mainly a Vista only problem seen there when having over 2gb installed and people wanted 4, 6, and 8gb set ups.

 

These are Fujitsu Lifebook S6420 laptops (32Bit) donated to us - they are very fast and solid business quality machines.

I picked up the tip of taking out a bank on an other forum, and I was quite amazed when it worked - no-one can really explain why!

I will probably buy one 4GB memory module just to see how things work out - the cost is not huge.

 

How much was installed and which flavor of 10 Pro 32bit or 64bit was going on them? It's likely something with the design there since the need to remove memory ahead of time was a drawback not seen in years now having been a Vista x64 issue while some chipsets, are known to cause problems. Once 10 is on however you should be able to max it out but only end up removing ram for each upgrade or fresh install down the line you run into.

 

I can't remember what build of W10 Pro I started with, but I used the Create Media method after four W7 upgrade failures - that is what caused me to search all sorts of forums, looking for an answer. I've had no problems with any of the laptops on W10 (doing updates regularly) till this fall update. There must be some characteristic of this one which makes it look like a major upgrade.

I can get my head around doing the memory thing for the initial installation, but I am disappointed at the recurrence of the same issue. I will need to call all the laptops back in for updating, which is a pain.

There are 2 banks of 2GB memory.

 

I was running the Tech Preview build as 10 was first labeled back in January on a VM. But I got side tracked a bit for other reasons and when going to get VM Player running I had to go for the VM Player 7.2 released on June 15 to run the 10240 build on which was permanently replaced by the Workstation 12 Player now seen with VM Player and Player Pro being replaced with Workstation Player Pro simply adding Workstation into the name as well as no longer seeing any strictly non commercial only version which threw people off a bit at first. Everyone had been used to a free version which now sees the option to buy the full commercial license.

By July of course when prepping for the release not having any running build to upgrade from I had to download the 10240 and then set that over time for the Insider Builds I just finished upgrading the 10586 VM that was activated with a 7 product key no less while the TH2 wouldn't accept it. The upgrade to the TH2 however transferred the Digital entitlement over from the 10586 on the spot without any problem seen there.





And yet a 7 VM I wanted to try the Genuine Ticket option from when wiping to see a fresh TH2 install on VM which is already on one wouldn't activate. But that's nothing new for 7 there even on Hyper-V on the 10 Insider side of the dual boot with 7 and not VM Workstation 12 Player where the 10 VMs are being run on the 7 side of the equation. Just another headache I guess not being able to activate a 7 VM on the same machine 7 is already on!

As far as your situation this nothing over 2gb or one Sodimm problem is out there alright since this was a plague dated backward to the Vista years before 7 came along with a working solution for the 64bit side of life. That will be a royal pain for you without any doubt making you a hardware removal for Windows install specialist! Isn't it wonderful?
(like freaking.... it is!*Mad )(i can imagine the reaction to finding all that out.*Sad )

 

My second laptop failed several times, so I have used my update fix and it seems to have worked.
I know, I could have used ISO, but I prefer to solve the problem, rather then to find a workaround.

 

On all laptops and computers in my house upgraded via windows updates no trouble at all and all working fast and how we want them.
Printer working as it should and mail app opening faster.

 

Mine fails, stops at 66% on the WU, if MS doesn't fix it then I'll stay on the initial RTM, 10240, also the Windows Defender definition update says it fails, but the application shows it's updated.

I'm not going to download an iso to update W10, W10 is supposed to be updated from WU, not from an iso. If MS wants all W10 updates to be handled with windows update, they'll need to make it work all the time every time.

I have an iso of 10240 in case I needed to repair W10 since my computer has no recovery drive.

I updated to W10 home from Win7 home with no problems via WU, all updates since that time in early Aug. have had no problems, only this most recent TH2. Other than that issue no other problems to note with W10, seems very stable, most things that ran on Win7 run fine on W10. Only really noticeable difference is the appearance, I used aero on 7.

 

Mine kept doing that, and then reverting back to the earlier version.
I had to do a clean install, the error message said something about migrating data !!

 

I would simply go to MS directly and download the updated MediaCreationTool.exe no longer seeing the _86 or _64 tail added on before the exe file extension from a single link for download of the ISO or creating the media not the immediate online upgrade there either but to see the media or iso option. You can right click on the "Windoews.iso" once saved to a folder on the drive and double click the setup.exe file to begin the upgrade! The media will you to see a fresh clean install take place however generally insuring the best results!

On the laptop that was upgraded from the 32bit 7 Home Premium to first the 32bit 10 Home followed by the clean install to watch that activate I then simply replaced the 32bit with the next 64bit Home clean install that activated on the spot never once entering a key since that took the OEM eprom information and activated automatically while the initial upgrade was a fright! But I was expecting that and later when not able to expand or move the OEM primary after removing the no longer needed System Reserved 300mn. OEM Recovery 400mb, and 3rd party 400mb partition. That was then nuked entirely to see the second 64bit 10 Home clean install take place and again activated automatically by DE! Digital entitlement being the new MS ball game for activation now seen.

The download you now see using the updated MC tool if not downloading the "GetWindows10-sds_____..exe" file replaces the need to create a 4 in 1 media downloading the previous 32/64bit Home or Pro iso and then clearing out the 32bit and 64bit folders once written to a flash drive larger then 4gb being 5.6gb in size like an 8gb you then extract the files from the two Home and Pro iso dual edition iso in two flavors into each folder. No now you simply pick Windows 10 not Home. Home N, Pro, Pro N, or Single Language being the 32bit Home edition only there still the last option to follow Windows 10 or Windows 10 N or KN you simply choose fhe first which when run will automatically detect the present 10 install and select the same flavor as well as edition! It's a new 4 in 1 download that comes in slightly smaller at 5.48gb including both Home and Pro editions as well as simply selecting 32bit or 64bit when going to see a clean install. The method is still same where you can see either a clean install or upgrade install while booted live from the 10 media. The upgrade install should take a full hour give or take depending on how much you presently have on.

• Get Windows 10
  
  
  

 

Read more: http://news.softpedia.com/news/windo...s-496202.shtml

 

They aren't exactly on the cutting edge for breaking news are they *Smile

 

I already - some user but maybe not! *Smile

 

I meant softpedia not you. I like it you take the time to post these news stories - keep 'em coming *Smile