A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Transferring existing Win10 installation



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old July 20th 18, 04:58 AM posted to alt.comp.os.windows-10
...wÂiñ§±¤ñ
external usenet poster
 
Posts: 6
Default Transferring existing Win10 installation

From: ...w¡ñ§±¤ñ

Paul wrote:
...w¡ñ§±¤ñ wrote:
Paul wrote:

I don't think the idea is to transfer the license. The
license is a separate issue the OP will have to deal
with himself.

And fat chance of it working.


Assuming some method works(doesn't matter which one, just that it does)
for moving an o/s then activation still comes into play.
My response was to alert two key points
The given that we all know
1. Retail licenses - upgraded from a qualifying o/s and/or Win10 retail
media - are transferable
2. OEM licenses are not transferable

#1 is pretty straight forward - the activation server knows the underlying
license was retail and transferable thus activation almost always succeeds

#2 slightly different, the activation server still knows the underlying
license was not retail, but OEM, and not transferable thus activation can
be problematic.

When activation fails the alternatives is 'phone home' based.* Those
'phone home' methods are exception mechanisms.

Since 1607, MSA was added....and yes, another exception mechanism via the
Activation Troubleshooter.

The reason why we see successful reports of OEM o/s being transferred is
due to an exception being made(either automatically or verbally by a CSA
agent).
*- the exception failure or approval lies on that fine line on abuse or
lack or abuse existing, respectively.

Use of the MSA(on the o/s prior to any significant hardware change - i.e.
that big square board) increases the potential success of an exception
being approved(on Retail and, yes, OEM).

That MSA linkage is there for a reason...thus anyone considering moving
and o/s(regardless of the license type) should take advantage of the
additional opportunity the MSA provides.


Thanks for the update. I'm sure Tumppi can profit from it.

*******

Purely for it's comedic value, I made some progress on Sysprep.

This web page claims the fix for MiracastView can be achieve
with an SQL database editor.


http://alexappleton.net/post/1597027...reless-display
-media


Well, I tried that, and it didn't work. I flipped a single bit
which was supposed to imply no account was using the thing,
and it still wasn't the solution. I've also been watching Sysprep
with Procmon, to catch it making references to MiracastView and
there were no direct reads that pointed to any other source.

So when the alexappleton.net solution didn't work, I just deleted...

C:\ProgramData\Microsoft\Windows\AppRepository\Sta teRepository-Machine.srd
** ... and the two like-named journal files, which are smaller.

I deleted those "offline", not while the OS was running.

The next time I booted that clone of Win10, a few items were
missing from the Task Bar :-) So this is hardly a perfect
solution by any stretch of the imagination. But when I ran

** %windir%\system32\sysprep\sysprep.exe /generalize /oobe /shutdown

it worked! The machine shut down at the end of the sequence.

If I wanted, I could take that disk over to this machine,
boot up, and the Digital Entitlement on this machine
should help to Activate it.

I'm not going to do that just yet though.

So the message so far, is the information upsetting Sysprep
is likely to be in StateRepository-Machine.srd . It's also
in other places that don't matter (the Registry). But
whatever is in that SQL Database, something other than the
single field alexappleton.net suggested ("IsInbox" = 0)
needs to be edited.

** Paul


Nice. Thanks for reporting the progress and details.

Also, I forgot to mention MSFT is certainly aware there are other variables
that come into play for OEM licensed machines(pre-installed by major
retailers or pre-installed by a System Builder shop)
- End-User takes machine to shop or OEM servicing center (warranty or not)
and ends up with a new mobo
- Shop(not OEM servicing center) fixes device and uses a VL to
reinstall/clean install and activate Win10 instead of using the original
sold OEM license/product key

In the case of the latter, some of that exception process might also take
the form of aiding the end-user to return to a non VL license which once
activated replaces the device's and VL licensing info.
-i.e. MSFT makes the end-user happy, then separately addresses the more
costly issue - the VL abuse by the shop that used the VL.



--
...w¡ñ§±¤ñ
msft mvp windows experience 2007-2016, insider mvp 2016-2018


--- Internet Rex 2.31
* Origin: The gateway at Omicron Theta/2 (1:261/20.119)

Ads
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 08:24 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.