I upgraded from win 8.1 pro (oem) to win 10 home, i want to - Microsoft Community

-

upgraded win 8.1 pro (oem) win 10 home, want upgrade pro product key not accepted.  how should proceed?

how did upgrade? free win 10 upgrade should've recognised win 8.1 pro & given win 10 pro.


Windows / Windows 10 / Windows update, recovery, & backup / PC



Comments

Post a Comment

Popular posts from this blog

Windows 7 professional reset to factory settings - Microsoft Community

-
Image
how on desktop pc reset windows 7 professional factory settings hi, if came preinstalled: here key/s press @ boot t(new condition). under each manufacturer in list below instructions in respective links follow on how use recovery partition acer – press left alt + f10 keys. http://acer.custhelp.com/app/answers/detail/a_id/2631 advent – tap f10 until starting system recovery appears https://answers.yahoo.com/question/index?qid=20081221054701aajt8yv asus – press f9 http://support.asus.com/troubleshooting/detail.aspx?slanguage=en&m=x53e&os=&no=1775 dell – press f8 bring advanced boot options                        http://www.dell.com/support/troubleshooting/us/en/19/kcs/kcsarticles/articleview?docid=dsn_362066 emachines : press left alt key + f10 http://techchannel.radioshac...
Read more

Error 8233 Microsoft Windows security -spp - Microsoft Community

-
log name:      application source:        microsoft-windows-security-spp date:          26-mar-17 5:52:03 pm event id:      8233 task category: none level:         warning keywords:      classic user:          n/a computer:       description: rules engine reported failed vl activation attempt. reason:0xc004f074 appid = 0ff1ce15-a989-479d-af46-f275c6370663, skuid = b322da9c-a2e2-4058-9e4e-f59a6970bd69 trigger=timerevent event xml: <event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">   <system>     <provider name="microsoft-windows-security-spp" guid="{e23b33b0-c8c9-472c-a5f9-f2bdfea0f156}" eventsourcename="software protection platform service" />     <eventid qualifiers="16384">8233</eventid> ...
Read more