Forum Home
Press F1
Thread ID: 147343	2018-11-18 23:37:00	W10 upgrade from 1803 to 1809just will not happen today for me.	kioti (17360)	Press F1

Post ID	Timestamp	Content	User
1455702	2018-11-18 23:37:00	More trouble that its worth really...... after installing W10 x64 Pro v 1803 to a 1TB unallocated space HDD from a Easeus Todo Full Backup, I then try to upgrade that v1803 to v1809 and fail to do so because I am being told that I cannot instal to the drive and save settings/apps etc etc because the drive is in an unknown location! Here is a pic of what I get when I try to upgrade either from Mounted ISO or burned DVD of the Dl's v1809 ISO got using the mediacreation tool 1809. www.dropbox.com NG?dl=0 I have had some real grief with this W10 OS I m trying to get up and running but I won't go into details here about the previous instals and corruptions etc etc. I will just give the details of the one I did today. Finding on restart of computer today the fresh installed from easeus todo backup of w10 v1803 and upgraded to w10 v1809 using the mediacreation 1809 tool and direct upgrading the v1803 had failed to start today. Message onscreen said my computer has a problem and the only error code it gave was Stopcode: NTFS File. After a hour or 2 doing the suggested Repair disc and more I wiped the drive with intent to again instal from the esaeus todo full backup. I did both of those things and now when I try to upgrade the W10 x64 Pro v1803 to the v1809 as an Upgrade option, I get that info shown in the pic.'Why it is today doing that I have no idea and considering it worked fine doing the instal 1803 to 1TB Drive yesterday and then the upgrade to v 1809 directly as it was Dl'd in the creation tool I don't know what the problem is with it today. In fact when it upgraded yesterday it intimated it was going to do it on the fly (or that was my inference of what was shown onscreen) it didn't do it on the fly...it took almost 3 hours for it to upgrade the v1803 to v1809.... 1 hour downloading it (which I thought it was upgrading and not downloading but it had DL's the ISO) and then a further 2 hours doing the Upgrade/Downloading updates and getting them installed and sorted out and then the Lets Get Started bla bla stuff all again. And now today it doesn't open to W10 v1809, says its problems (STOPCODE : NTFS File) and gives me a merry run around when I wipe it off the HDD and reinstal the 1803 and try upgrade that and get the screen as per the pic. The only thing I can imagine why it is saying the location is somewhere else could be because yesterday when I did the reinstall of v1803 using the esaeus todo backup was that I had done that using the easeus WinPE disc and today I did the reinstall of w10 v1803 from the easeus todo backup from the open into W10 v1803 and the easeus todo backup is on the external HDD and the Easeus todao backup app is on the HDD that is NOT the 1TB HDD to which the easeus backup was installed. Longshot that one and a shame I cannot remember exactly what process I used to get the Backup of the v1803 onto the 1TB Drive. Maybe its going to be a long haul day trying out all the options. Or at the end of the day, I wipe the drive again which I am going to have to do, get W10 v1803 installed and forget about the upgrade to v 1809. I am getting really peeved with this W10 fiasco I am being given the runaround attempting to get sorted out.	kioti (17360)
1455703	2018-11-19 01:01:00	There's obviously some serious corruption someplace. With the picture provided -- Any reason the Seagate External Drive is attached? In the previous post I suggested MAKE SURE NO other drives are connected, including any USB backups, :D the easeus todo backup is on the external HDD and the Easeus todao backup app is on the HDD that is NOT the 1TB HDD to which the easeus backup was installed. Having the backup on the external drive is fine, but it should be disconnected once its been restored. The other HDD's -- basically sounds like things are really in a bit of a fuddle as far as windows is concerned as to whats where. :waughh: Ideally, the 1TB drive should be empty, a bootable CD made from the EaseUS software, the working HDD shouldn't be attached (only a blank 1TB & backup USB drive) boot from the CD, drop the image back, reboot and remove the external HDD at the same time. Having the USB connected still while attempting to upgrade is similar to having a second drive internally attached, W10 is capable of locating and installing on A USB drive, which is not what is wanted in this case. Another possible Problem -- The backup copy / clone of 1803, if The image/backup was created when the two hard Drives were connected then any corruptions / faults, settings etc will be carried over to the image, so while its a excellent Idea to have made a Backup :thumbs: It may actually be no good, as its possible you're putting a bad image back over a current bad install. You can try making a bootable CD from the EaseUS software you pictured, it has the same Partition check as per the suggested fix www.easeus.com If the System is to badly corrupted it WILL be unstable, and wont fix its self or anything you do can be a waste of time. Over the years you learn quickly how long to "keep trying" before finally doing what you should have done before-- Save any data, wipe the drive completely clean do a fresh install. Sometimes a damaged OS simply cant be repaired( that's ANY OS) Simply start from fresh, install should take around 20- 30 minutes, W10 generally will install drivers on its own or if you have them from the manufacture - replace any data / programs. If you manage to get it booting again, you "may" be able to run some dism commands to repair, but I wouldn't hold my breath on fixing it completely. The command from CMD / Admin dism /online /cleanup-image /Restorehealth	wainuitech (129)
1455704	2018-11-19 01:10:00	Over the years you learn quickly how long to "keep trying" before finally doing what you should have done before-- Save any data, wipe the drive completely clean do a fresh install. Sometimes a damaged OS simply cant be repaired( that's ANY OS) as above. Cut your losses. if you really want 1809 (why, given all your issues) then wipe & do a clean install Also, the image you are using may have been from a slightly corrupt/flaky/unstable Windows .	1101 (13337)
1455705	2018-11-19 01:32:00	as above. Cut your losses. if you really want 1809 (why, given all your issues) then wipe & do a clean install Also, the image you are using may have been from a slightly corrupt/flaky/unstable Windows . The image backup is fine. It instals and runs. that is the v1803 backup. I installed it yesterday and it works just fine and as I said I upgraded that to v1809 and that was just fine Until I rebooted the computer today and it was stuffed.	kioti (17360)
1455706	2018-11-19 01:41:00	There's obviously some serious corruption someplace. With the picture provided -- Any reason the Seagate External Drive is attached? In the previous post I suggested :D Having the backup on the external drive is fine, but it should be disconnected once its been restored. The other HDD's -- basically sounds like things are really in a bit of a fuddle as far as windows is concerned as to whats where. :waughh: Ideally, the 1TB drive should be empty, a bootable CD made from the EaseUS software, the working HDD shouldn't be attached (only a blank 1TB & backup USB drive) boot from the CD, drop the image back, reboot and remove the external HDD at the same time. Having the USB connected still while attempting to upgrade is similar to having a second drive internally attached, W10 is capable of locating and installing on A USB drive, which is not what is wanted in this case. Another possible Problem -- The backup copy / clone of 1803, if The image/backup was created when the two hard Drives were connected then any corruptions / faults, settings etc will be carried over to the image, so while its a excellent Idea to have made a Backup :thumbs: It may actually be no good, as its possible you're putting a bad image back over a current bad install. You can try making a bootable CD from the EaseUS software you pictured, it has the same Partition check as per the suggested fix www.easeus.com If the System is to badly corrupted it WILL be unstable, and wont fix its self or anything you do can be a waste of time. Over the years you learn quickly how long to "keep trying" before finally doing what you should have done before-- Save any data, wipe the drive completely clean do a fresh install. Sometimes a damaged OS simply cant be repaired( that's ANY OS) Simply start from fresh, install should take around 20- 30 minutes, W10 generally will install drivers on its own or if you have them from the manufacture - replace any data / programs. If you manage to get it booting again, you "may" be able to run some dism commands to repair, but I wouldn't hold my breath on fixing it completely. The command from CMD / Admin dism /online /cleanup-image /Restorehealth wainuitech the external drive is there in the pic because I had used it to attempt the upgrade to v1809 where the ISO is stored. I hadn't unplugged it when I tried to do the upgrade and got that message shown in the pic and I was loopeing the ISO to do the upgrad e from the open 80 GB HDD with v1803 running I'm wiping the entire1TB Disk again and going to attempt instal the v1803 backup I made by using a WinPE disk I created from Easeus. If that doesn't work I will stick with this 80GB HDD with 10 v1803 and any new apps etc I instal I will do so to an HDD specifically for that purpose. The Backup image of the 80GB HDD W10 v1803 was created when only that HDD was connected to the computer...well that is not 100% correct...the 80GB HDD was connected as well as the Seagate external drive for me to save the backup to because it was stressed to NOT save the backup to the HDD that the backup is making an image of. Also, After I had upgraded the 1TB HDD to the v1809 I rebooted it twice to make sure that it would get back into a working W10 Desktop and it did. Then I shut down the computer, rebooted it today and got the STOPCODE:NTFS File" appear onscreen. So I scrapping the whole contents of the 1TB and starting again...attempting to load the backup of C drive (80GB W10 v1803) using the easeus WinPE disk I created.	kioti (17360)
1455707	2018-11-19 03:39:00	fossbytes.com	1101 (13337)
1455708	2018-11-19 03:50:00	Ok. Here is the last of it. I have installed the W10 x64 Pro v 1803 onto the 1TB drive and it is working fine. At the moment I am in the 80GB W10 v1803 HDD solely for the purpose of coming here to Press F1 to do the update of info. As I explained in another thread, when I am using the 1tb HDD version of W10 x64 Pro I cannot sign into my Press F1 account using any Browser at all. I have contacted Admin about that issue and asked them to delete the old account had into which somehow my log in to Press F1 is locked. As of yet I have not had any response from Admin. When I use either this 80-GB HDD version of W10 v1803 or the 1TB HDD W10 v1803, I can only have 1 of the HDD's connected to the computer and it would seem that the only reason I have to come to this 80GB Drive is to be able to log into Press F1. Believe me, having to shut down the computer and disconnect 1 HDD and connect another HDD and reboot going into BIOS to change the Boot to HDD that I want to use is time wasting annoyance. See what happens here in the next restart of Computer and if the 1TB Version of W10 starts playing the lets give this guy some !@#$ because he's insulting W10 by using NO INTEL Hardware at all!! And as we all at W10 know, We were Created and so were new Hardwares that are strictly INTEL manufactured to be used for us to RUN Efficiently. AMD-Gigafright-Seagate-DDR3!!!!!! As for upgrade to v1809?????? Somewhere over the rainbow maybe. Rant over.	kioti (17360)
1455709	2018-11-19 04:28:00	fossbytes.com 1101 Thanks for the link. Bells are ringing :D Oh and after I did the instal of v1803 to the 1TB HDD a short time ago I had a pop up come onscreen after I booted into it and said an App of Folder of mine cannot be used because it has been 'Moved'.............I thought this 'New' 1809 release that is only a few days old had addressed those bugs that had manifested themselves in the initial 1809 release that was quickly shelved and withdrawn from Windows Download sites. I will shrug for now and wait until the New 1809 is proven infallible by all the other Free Beta Testers M$ rely upon to make their 'Updates' good to go. :D	kioti (17360)
1455710	2018-11-19 04:38:00	When I use either this 80-GB HDD version of W10 v1803 or the 1TB HDD W10 v1803, I can only have 1 of the HDD's connected to the computer If you have two HDD's both with bootable OS's, basically its trying to Dual Boot, which since its not setup to do so is causing confusion in the boot sequence. :)	wainuitech (129)
1455711	2018-11-19 07:39:00	If you have two HDD's both with bootable OS's, basically its trying to Dual Boot, which since its not setup to do so is causing confusion in the boot sequence. :) wainuitech....... I have the 2 OS's on independent HDD's and it is pre POST that I enter BIOS/SETUP and choose which HDD to boot from, so I don't really understand how there can be any confusion in the Boot Sequence. You're the Tech and I respect what you say but as I said, as I choose the HDD to Boot to in BIOS how can it get confused? Unless perhaps I need a new CMOS Battery and BIOS isn't holding fully what it has been instructed to do. Kinda like if I get into a car and start it, put the gear stick in the Reverse position and release the clutch and the car moves forward well something in the transmission is pukaru, or I'm pithed. "Ours is not to wonder why. Ours is but to do and die"	kioti (17360)
1 2