1 |
Hi Mark, |
2 |
was your old version Win10 PRO" as well? - as far as I know a |
3 |
reinstall will only validate if the hardware as recorded at MS mostly |
4 |
matches and its the same version. Cloning via dd, then running through |
5 |
the re-validation checks, then making changes in small steps is the only |
6 |
way I have been able to make it work despite what is written in the link |
7 |
below. |
8 |
|
9 |
Also check out: |
10 |
https://www.techrepublic.com/article/windows-10-will-microsoft-charge-you-if-you-need-to-reinstall/ |
11 |
|
12 |
BillK |
13 |
|
14 |
|
15 |
On 7/1/20 7:37 am, Mark Knecht wrote: |
16 |
> Michael, |
17 |
> I got Win 10 Pro installed via the M$ tool that creates USB install |
18 |
> devices. It worked fine. Reading online it seems that if M$ sees the |
19 |
> new disk as still the same 'hardware' then it's supposed to |
20 |
> automatically validate and I'd be good to go. so far, after 2 hours it |
21 |
> hasn't done that but I'll give it awhile and see what happens. As it |
22 |
> only took an hour I might still try the disk copy path and see if that |
23 |
> comes up validated as that would also transfer the couple of |
24 |
> applications I have on the original hard drive. |
25 |
> |
26 |
> Anyway, thanks for the ideas. |
27 |
> |
28 |
> Cheers, |
29 |
> Mark |
30 |
> |
31 |
> On Mon, Jan 6, 2020 at 3:01 PM Michael Jones <gentoo@×××××××.com |
32 |
> <mailto:gentoo@×××××××.com>> wrote: |
33 |
> |
34 |
> You can use the Windows 10 Download Tool (Or similarly named |
35 |
> thing, sorry, I can't find the details of it at this time) to |
36 |
> download an ISO image |
37 |
> |
38 |
> Combine that with the rufus program https://rufus.ie/ (I use the |
39 |
> portable one, personally) to create a Windows 10 USB installer stick. |
40 |
> |
41 |
> On Mon, Jan 6, 2020 at 2:39 PM Mark Knecht <markknecht@×××××.com |
42 |
> <mailto:markknecht@×××××.com>> wrote: |
43 |
> |
44 |
> Hi Michael, |
45 |
> Thanks for the response. Great info. |
46 |
> |
47 |
> The install Win 10 clean sounds wonderful if it works. With |
48 |
> no DVD in this machine it sounds like I should investigate an |
49 |
> install from USB if the machine supports it. It's an Asus |
50 |
> gaming laptop circa 2008 so hopefully that works but I've |
51 |
> never done it on this machine. |
52 |
> |
53 |
> Cheers, |
54 |
> Mark |
55 |
> |
56 |
> On Mon, Jan 6, 2020 at 12:56 PM Michael Jones |
57 |
> <gentoo@×××××××.com <mailto:gentoo@×××××××.com>> wrote: |
58 |
> |
59 |
> Generally the way I've handled this situation in the past |
60 |
> is like so (this is written from memory, so expect |
61 |
> gratuitous problems). |
62 |
> |
63 |
> On the machine with the drive attached |
64 |
> mbuffer -i /dev/mydrive | xz -e -9 | mbuffer -O hostname:port |
65 |
> |
66 |
> On a machine with storage space |
67 |
> mbuffer -I port -o /path/to/storage.xz |
68 |
> |
69 |
> To make a backup. |
70 |
> |
71 |
> |
72 |
> In terms of cloning windows to another harddrive in |
73 |
> general, as long as the destination harddrive is large |
74 |
> enough to fit the original drive without issues, simply |
75 |
> running: |
76 |
> |
77 |
> dd if=/dev/original of=/dev/destination |
78 |
> (I prefer dcfldd, personally) |
79 |
> |
80 |
> Is enough. Run gparted (the graphical version, for nice |
81 |
> wizards) after, and it'll fixup your partition table for |
82 |
> you to match the new size, and you can re-size any |
83 |
> partitions you have to make them match as well. I do |
84 |
> exactly this all the time and have yet to have a problem. |
85 |
> |
86 |
> As for windows 10 licensing, don't trust me on this |
87 |
> blindly, but your license should be tied to the hardware |
88 |
> fingerprint of the laptop. So even installing windows |
89 |
> fresh on your new SSD should result in Windows activating |
90 |
> automatically. In fact, you might want to take this |
91 |
> opportunity to try that out, to get a completely fresh |
92 |
> installation without the decade of old cruft built up by |
93 |
> window's lack of a package manager. |
94 |
> |
95 |
> If it doesn't activate as soon as you plug in an ethernet |
96 |
> cable, you can just wipe your SSD and copy your old |
97 |
> installation as discussed already. |
98 |
> |
99 |
> |
100 |
> |
101 |
> On Mon, Jan 6, 2020 at 1:11 PM Mark Knecht |
102 |
> <markknecht@×××××.com <mailto:markknecht@×××××.com>> wrote: |
103 |
> |
104 |
> Hi all, |
105 |
> I haven't been here in a couple of years. IT's |
106 |
> great to see some familiar names posting. Cheers to all. |
107 |
> |
108 |
> I have a laptop running Win 10 with no (working) |
109 |
> DVD/CDROM. For various reasons I want to move from a |
110 |
> 10 year old laptop drive to a new SSD and am looking |
111 |
> for guidance on I might do that. Win 10 is properly |
112 |
> licensed but through a weird channel - it was Win 7 |
113 |
> that M$ allowed to convert to Win 10 for free and I'm |
114 |
> nervous that if the hard drive died I'd have to |
115 |
> purchase a new license as the free conversion path |
116 |
> likely doesn't exist anymore. |
117 |
> |
118 |
> Both drives are nominally 500GB. |
119 |
> |
120 |
> The older hard drive fdisk info shows: |
121 |
> |
122 |
> root@science:~# fdisk --list /dev/sde |
123 |
> Disk /dev/sde: 465.8 GiB, 500107862016 bytes, |
124 |
> 976773168 sectors |
125 |
> Disk model: ASM1053E |
126 |
> Units: sectors of 1 * 512 = 512 bytes |
127 |
> Sector size (logical/physical): 512 bytes / 512 bytes |
128 |
> I/O size (minimum/optimal): 512 bytes / 512 bytes |
129 |
> Disklabel type: dos |
130 |
> Disk identifier: 0xe0c5913d |
131 |
> |
132 |
> DeviceBoot Start End Sectors SizeIdType |
133 |
> /dev/sde1 63 45062324 45062262 21.5G |
134 |
> 1c Hidden W95 FAT32 (LBA) |
135 |
> /dev/sde2 * 45062325 288063133 243000809 115.9G |
136 |
> 7 HPFS/NTFS/exFAT |
137 |
> /dev/sde3 288063488 289247231 1183744 578M |
138 |
> 27 Hidden NTFS WinRE |
139 |
> /dev/sde4 289249254 976768064 687518811 327.9G |
140 |
> fd Linux raid autodetect |
141 |
> root@science:~# |
142 |
> |
143 |
> The Linux RAID autodetect is from running Gentoo at |
144 |
> some earlier time and probably doesn't need to be |
145 |
> copied. I'm not at all sure what /dev/sde3 is or |
146 |
> whether it's required to make M$ happy. |
147 |
> |
148 |
> The new SSD is unused and shows: |
149 |
> |
150 |
> root@science:~# fdisk --list /dev/sdf |
151 |
> Disk /dev/sdf: 465.8 GiB, 500107862016 bytes, |
152 |
> 976773168 sectors |
153 |
> Disk model: ASM1053E |
154 |
> Units: sectors of 1 * 512 = 512 bytes |
155 |
> Sector size (logical/physical): 512 bytes / 4096 bytes |
156 |
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes |
157 |
> root@science:~# |
158 |
> |
159 |
> The appear to have the same sector count and |
160 |
> overall size. |
161 |
> |
162 |
> I can make a 1TB drive available in my big machine |
163 |
> and work over USB (which is what I'm doing to get the |
164 |
> info above) but I'm unclear how much of this can be |
165 |
> done automatically and how much I might need to do by |
166 |
> hand. |
167 |
> |
168 |
> As long as I don't hurt the old drive I can put |
169 |
> data on the SSD multiple times to get through the |
170 |
> process in case I have trouble. |
171 |
> |
172 |
> Does anyone have experience with this sort of issue |
173 |
> and can you point me toward some instructions I might try? |
174 |
> |
175 |
> Thanks, |
176 |
> Mark |
177 |
> |
178 |
> |