New
#21
re:NavyLCDR said:
I did the update to RTM on the win 7x64 primary partition it worked but required a few re starts to find everything and smooth out although it could boot faster .
I re set the hdd indexing on the updated parition and excluded library and media files and just indexed the user files ,browsers and DOCS and ofc not the programs .
I renamed the updated win 10 RTM drive partitian to Win 10 C: from Win 7 C: *after the update* that was a mistake ☻
The boot loader got confused and booted into the pre existing Win 10 insider build no matter which option I selected from the boot loader . One option said Windowes 10 on volume 2 and the other was Windows 10 on volume 3 .
Changing the new Win 10 RTM partition ( actually the pre existing Win 7 drive partition name *back to* Win 7 C: fixed it ......it just looks odd in the directory tree now that this is a Win 10 /Win 10 configuration because whatever drive *I'm not on* is a win 7x drive but othewise it works fine now .
The boot loader options remained unchanged from above after the update throughout all of this and they work as intended now .
My take away is dont rename the RTM in place updated drive partition from win 7 C: to Win 10 C: *after the RTM in place update * on a dual boot configuration and just let it be ☻☻
I may do a clean install later if the boot time doesent speed up some or I may do it just because it's Windows although the win 7 clean install was in good shape I did that and a clean install of a test build on a new drive about 6 mo. ago .
Friday I'm doing a bare metal install of Win 10 RTM ISO on the i7 HP Elite book laptop with updated drivers from HP that has an activated Win 10 RTM update over 7 x64 pro to get it off on the right track .
I may re set that one to a UFEI configutration it goes both ways, it's on a reg bios now ...any comments on that would be appreciated .
OTOH I might try a clean install re set on the RTM partition on *this box * just to see what shakes out that way later on .
I mostly use the test biuld on a smaller partition here on this box (daily driver ) on a 150 GB partition and the big parition that has RTM on it now mostly for storage anyaway , it runs pretty fast that way .
OTOH maybe we'll juast see what shakes out after I get the boot time back to speed or it may work itself out I've seen that happen on test builds that otherwise worked fine like this one .
On this daily driver 4 core I can see RTM on a 240 GB SSD drive with some x86/64 programs on it and *this * 1 TB metal hdd as storage with the Insider test build on it until the program ends maybe who knows ?
Anyways thanks for the replies .☺
Last edited by blutos cousin; 17 Sep 2015 at 02:03.