• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Now that W10 is out, are you a W7 / W8 refusenik?

Now that W10 is out, are you a W7/W8 refusenik?


  • Total voters
    271
Status
Not open for further replies.
I've had the permissions issue before. For some reason permissions on folders from older OSes to a fresh 10 install can create some headaches. Resetting permissions seems to help though.

https://www.reddit.com/r/Windows10/comments/3g42rn/updated_to_windows_10_now_im_getting_access/

Be careful giving everyone full control, that could bite you in the ass in the future. I have dealt with the same issue though. If they are on a drive, you might modify permissions for your account. Some users skip using a Microsoft Account and use a local account which helps resolve the issue. I was able to resolve it and continue using my MS account by doing the above. I made sure my MS account is under the Administrators security group, reapplied permissions to Administrators. It did take a couple of tries but I was able to resolve it.
 
By the way found this on Microsoft website...
So Could I reinstall W8 on one of my other empty drives in this system, activate w10 and then go back to this OS install on my SSD?


  • You performed a clean installation ofWindows 10 instead of first upgrading from your previous version of Windows. When this happens, we aren't able to register your entitlement with the activation servers because you aren't upgrading to Windows 10. To fix this, go back to your previous version of Windows, make sure the previous version is activated, and then upgrade to Windows 10. For more info about how to go back to a previous version of Windows, see the section in Recovery options in Windows 10.


I've had the permissions issue before. For some reason permissions on folders from older OSes to a fresh 10 install can create some headaches. Resetting permissions seems to help though.

https://www.reddit.com/r/Windows10/comments/3g42rn/updated_to_windows_10_now_im_getting_access/

Be careful giving everyone full control, that could bite you in the ass in the future. I have dealt with the same issue though. If they are on a drive, you might modify permissions for your account. Some users skip using a Microsoft Account and use a local account which helps resolve the issue. I was able to resolve it and continue using my MS account by doing the above. I made sure my MS account is under the Administrators security group, reapplied permissions to Administrators. It did take a couple of tries but I was able to resolve it.

What permission do you recommend instead of everyone? New to this problem
 
By the way found this on Microsoft website...
So Could I reinstall W8 on one of my other empty drives in this system, activate w10 and then go back to this OS install on my SSD?


  • You performed a clean installation ofWindows 10 instead of first upgrading from your previous version of Windows. When this happens, we aren't able to register your entitlement with the activation servers because you aren't upgrading to Windows 10. To fix this, go back to your previous version of Windows, make sure the previous version is activated, and then upgrade to Windows 10. For more info about how to go back to a previous version of Windows, see the section in Recovery options in Windows 10.


You can probably install over if you got all your data backed up. Then do upgrade option. Also a good thing to do would probably make a image of the OS for backup.
 
@Delta6326

Give full permissions to administrators, and then add yourself to the administrators group in Computer Management under Users and Groups (if you have a Pro OS version or higher). Everyone can have Read access, and really you can do whatever you want...but best practice and if other people have access to your shares, workstation or account (if left open or not passworded), then your files are at risk...both physically and remotely.



You could install 8 on an empty drive and upgrade to 10 yes. It will create a UID for your mainboard that registers the OS. Then your next fresh install should activate using that UID to check against MS's servers to verify you're legit.

Both fresh installs we did this morning were successful, with the latest ISO, one 7 key one 8 key, both Pro non-oem. Must be something with the key you have...some get flagged I guess. I'm hoping to duplicate that issue on my bench. :)
 
Talking to Mohammed Y
[COLOR=rgba(0, 0, 0, 0.6)]Microsoft Answer Tech

Asked for my W8 Pro key to activate it
[/COLOR]

asking for remote access?
 
Interesting... what if you temporarily remove the 360 and run both displays off of the 390 or even vice-versa?
Can't. 390 had no VGA support. The only option is DisplayPort (plug and play) to VGA (non-plug and play) converter and Windows ends up moving the crap on the second to display to the main display every time the monitor goes off (being it power saving or KVM switching). It's horrible which is why I've generally had a second graphics card in my machine for VGA since switching to R9 290X.

If I recall correctly, it ran perfectly fine with just the 360.

Has this issue plagued you since going to 10? Before 10? Or only after you'd been on 10 a while? And it seems to occur pretty consistently to your actions...is the KVM the type that you hit scroll lock or a key combo to switch or does it come with a remote button to swap inputs? I have seen some KVM's cause some issues because of how the outputs are detected... I've honestly had better luck with newer IOGear KVM's than older ones in W7/8/10, S2008/2012, R2, etc.
I believe it didn't do it when first upgrading to Windows 10. I think it started doing it after that big Threshold update around the beginning of November.

KVM supports scroll lock + scroll lock + # or pressing a physical button on the KVM itself. I always use the scroll lock shortcut. The KVM is a Startech model and I've had it for probably 7 or 8 years now.
 
@FordGT90Concept

Startech makes some decent KVM stuff...I can't imagine its the issue here, so I'll leave the assumption it isn't for now.

I can only speculate maybe an issue with the newer AMD drivers? Have you gone back to pre-crimson, pre-beta to see if that resolved it?

And nothing else in event logs related to anything else failing or switching? I wonder if the OS is lagging on detecting the VGA monitor and that's why its switching to single screen desktop mode...
 
Ok issued fixed! Great support He did remote access tried code 3 times, contacted supervisor he joined looked it over he typed in a brand new W10 Pro code typed it in a notepad for future reference.

The big question is my W8 Pro code still good? Could I do another pc build use it then upgrade :D


So in the future if anyone get's these error codes just click on the customer support link and do chat.
http://windows.microsoft.com/en-us/windows-10/activation-errors-windows-10



Now that it's activated found some updates in those was
Upgrade to Windows 10 Pro, version 1511, 10586.
So I must have DL'ed a old ISO.
Also I switched to "Metered connection" that way it won't auto download updates.
 
Last edited:
Theoretically the W8 code shouldn't work for 8, but I know before the ISO change in November that people were able to reuse their original OS activations for the original OSes they were for after using them to activate 10. Not sure that's long term tho. But with MS making such a big push to support 10 and only 10, they might not care as much while they ween support off of 7 and 8 progressively quicker with each passing month (it seems like...).

Glad you got it sorted! :)
 
Windows 8 Pro code is only good for Windows 8 Pro. You'd have to install Windows 8 Pro, upgrade that via Windows Update to Windows 8.1 Pro, then upgrade that via Windows Update to Windows 10 Pro, and finally activate that Windows 10 Pro install while connected to the internet (registering your hardware ID with Microsoft). Finally, if you don't like all that upgrade nonsense, you can do a clean install of Windows 10 Pro and, while connected to the internet, it should activate (using the previously stored hardware ID).

Windows 10 does not accept keys for any product other than Windows 10.

I can only speculate maybe an issue with the newer AMD drivers? Have you gone back to pre-crimson, pre-beta to see if that resolved it?
Nope but I probably should try it. Not sure if they'll like 3## cards though. I'm 90% sure it's something that changed in Windows though.
 
You're wrong. I just did fresh installs today with Windows 7 and 8 keys. I do so regularly.

http://windows.microsoft.com/en-us/windows-10/activation-in-windows-10

Starting with the November update, Windows 10 (Version 1511) can be activated using some Windows 7, Windows 8, and Windows 8.1 product keys. For more info, see the section Activating Windows 10 (Version 1511 or higher) using a Windows 7, Windows 8, or Windows 8.1 product key

This means that during a fresh install, you can use a Windows 7, 8 or 8.1 key. Apparently there are select keys where you will run into issues as @Delta6326 found out. I've installed over a dozen systems using fresh installations and previous windows OS keys with the new ISO. I wouldn't suggest it if I didn't have experience making it work first. Might as well take advantage of the free upgrade and now that you don't need to upgrade first (in most cases) there's less reason not to go to 10. ;)

Here's another snip from the link above:

During the free upgrade, you can use a valid Windows 7, Windows 8, or Windows 8.1 product key to activate Windows 10(Version 1511 or higher). The following types of product keys are supported:
  • Product keys included in the packaging or the Certificate of Authenticity (COA) attached to your PC that came installed with Windows.
  • Product keys included in the confirmation email you received after buying Windows from an online retailer.
  • Product keys included in the box the Windows DVD came in.
  • Product keys you bought using Windows Anytime Upgrade or Get Genuine Windows.
  • If you bought a Windows 8.1 Pro Pack product key, you can use it to activate Windows 10 Pro.
 
Windows 8 Pro code is only good for Windows 8 Pro. You'd have to install Windows 8 Pro, upgrade that via Windows Update to Windows 8.1 Pro, then upgrade that via Windows Update to Windows 10 Pro, and finally activate that Windows 10 Pro install while connected to the internet (registering your hardware ID with Microsoft). Finally, if you don't like all that upgrade nonsense, you can do a clean install of Windows 10 Pro and, while connected to the internet, it should activate (using the previously stored hardware ID).

Windows 10 does not accept keys for any product other than Windows 10.


Nope but I probably should try it. Not sure if they'll like 3## cards though. I'm 90% sure it's something that changed in Windows though.


That is not accurate.

I installed a windows 8 Pro system (OEM disc install) two weeks ago. After getting the thing to activate (internet activation didn't work, had to do it by phone) I went to the windows website and download 10 directly. About 45 minutes later 10 was up and running, without ever having to go to 8.1. The 8.1 upgrade might have resolved the online activation, but I never upgraded to 8.1.
 
Ok, now i need to find out how to fix all these "Group or user names"

On left is how a normal default file should look like "I think". On the right is a screwed up folder with pictures inside.
When trying to remove "Account Unknown" I get message at bottom.



I Disabled "Inheriting Permissions" On the TPU Logo Picture now I can't view it or change the owner...? *Fixed

I fixed it all up! Hope this helps anyone in the future.

Do this by right-clicking the Drive (In My Computer), > Properties > Security tab > then look towards the bottom right hand side and click "Advanced" > then click "Change" near the Owner > then type in the field below your "UserName" > then click "Check Names" > click "Ok" > then make sure that the checkbox next to "Replace owner on subcontainers and objects" is checked > now change your "Permission Entries" > click Add/Remove (what ever needs to be done) >click apply > then click Ok >

If that doesn't fix it all, then go back into it check the box (next to "Replace all child object permissions with inheritable permissions from this object") > then click OK

All files look like Picture

capture2016.jpg
 
Last edited:
Don't know then. I've heard of people not being to activate doing it directly that way. Maybe something has changed on MS' side since. I can only tell you what worked for me and from what I've observed.


Well i am going back to a month after it was released, and yes some did have issue's but i think the MS servers might of been over whelmed maybe even bug issues.

I was not trying to say your way would not work or should not be tried, i was just saying how it worked for me which i believe i have said in this thread back then too.

I be trying it again int he next week or so to see if it still works that way which it should.
 
people need to read you no longer need todo a upgrade install for windows 10
as of TH2 media refresh it will take a 7/8/8.1 key and activate
 
people need to read you no longer need todo a upgrade install for windows 10
as of TH2 media refresh it will take a 7/8/8.1 key and activate

Which is no true. Or more specifically, they don't tell you the small print. Maybe that works, but if they key is fresh, never used one (lets say you had one key laying in your drawer, unused). It won't work. I had such situation and I had to go through whole fuck of problems to install stupid ancient Windows 7 on brand new system so I could activate the god damn thing and use that key later in Windows 10. It works now, but I've needed damn 8 hours to do it because so many things were going wrong with the old OS when trying to install it.
 
I've used brand new 7 and 8 keys on 1511 W10 ISO's without the issues you faced, in fact just did so today, and even posted about it in this thread shortly after I did it. It's not definitive because it happened to you once, with that said I'm sure you aren't the only poor soul that's fought to make it work. I've deployed plenty of fresh 10 installs using recycled and (primarily) new and unused keys. It does sound like you went through a lotta BS, and it sucks you had to activate it first...maybe there's a regional issue there? I dunno...but ever since 1511 dropped I haven't had any issues doing fresh 10 installs using 7 and 8 keys. Maybe I've been lucky tho! :D

But even on MS's site, they are careful to use the word "some" keys. See my last post above where I quote and link to the site that details the upgrade options.
 
OEM keys can't activate Win10 directly unless they were used on Win7 or Win8 before, potentially they even have to be upgraded with Win10 at least once to be able to activate Win10 later on with that key.
 
And I'm back with more W10 issues, hope it's OK I'm posting on here.

My pc was working great after activation, it then found some updates, it was dl'ing them last night I wake up to come check it and it's not getting any internet...
So I dl'ed the latest WiFi drivers(W10) via phone and still didn't fix the problem.
It connects to my network and on another computer I can see it connected, but no internet. I can't even check my router on it... I can't even tether my phone internet.

Also noticed a ridiculous amount of event warnings and errors.

I never signed up for preview build?
 

Attachments

  • Capture2017.jpg
    Capture2017.jpg
    364.6 KB · Views: 313
  • Capture2018.jpg
    Capture2018.jpg
    129.8 KB · Views: 310
  • Capture2023.jpg
    Capture2023.jpg
    133 KB · Views: 276
Last edited:
What is the IP? Windows could of done its infamous private IP on ya. Its annoying when it has done that.

Try going into cmd and release the IP and renewing. Also, have you tried pinging the router?

Commands that might help you out:

ipconfig /all - show all the info on your IP settings
ipconfig /release - release your current IP
ipconfig /renew - get new IP from DHCP host
 
What is the IP? Windows could of done its infamous private IP on ya. Its annoying when it has done that.

Try going into cmd and release the IP and renewing. Also, have you tried pinging the router?

Your going to have to tell me how, I don't know cmd commands.

I'm debating on just going to the previous restore point. I only have a free programs and haven't done anything yet.
 
Your going to have to tell me how, I don't know cmd commands.

I'm debating on just going to the previous restore point. I only have a free programs and haven't done anything yet.
Just posted them above. Also doing help or ? in any terminal prompt is your best buddy.

Kind of the reason Linux and Unix based OSes don't scare me off. Then again I started dealing with a computer with Windows 3.1 MS-DOS.
 
I did run into an issue on my laptop with WiFi...I forget what I did to resolve it tho. Pretty sure re-ran updates. Can you connect via an Ethernet cable?

Also in your wireless properties, what if you force a static IP address and a static DNS (say Google's 8.8.8.8 and 8.8.4.4) and retest?

Researching Event ID's 201 and 202 in Google brought up quite a few forum posts on Technet, might be worth reading about.

To renew your IP address do this

Click start
Type CMD
Open CMD

Type ipconfig /release
push enter
Type ipconfig /renew
push enter

This will rely on your gateway's DHCP service to give it a new address. You can also disable and renable your wireless device in Network and Sharing Center > Change Adapter Settings as well. That sometimes will help to reinitialize.

Another option is go go into Device Manger, uninstall the device and check the box to remove the drivers. Reboot and see if that allows you to pick up the correct driver for your device or if you need to use..
 
ipconfig /all -
host grant
Node-hybrid
IP no
Wins proxy no
ipconfig /release - the operation failed as no adapter is in the state permissible for this operation.
ipconfig /renew- same as above

Wire connection would be long ways at least 100'

What's your thoughts on just doing a clean install now that my w10 key works? Only programs are motherboard drivers. Steam music, etc. On different HD
 
Last edited:
ipconfig /all -
host grant
Node-hybrid
IP no
Wins proxy no
ipconfig /release - the operation failed as no adapter is in the state permissible for this operation.
ipconfig /renew- same as above
Now that the first time I seen something like that. Definitely something screwy going on.

Currently looking up answer for this. But you may as well do a restore to see if that fixes the issue.

Was it showing a media disconnected in the ipconfig /all read out?
 
Status
Not open for further replies.
Back
Top