![]() ![]() I'm running out of ideas that you can use that don't entail you spending money on Windows 8.1 media and product key. So bottom line is, that you will not likely be able to do an inplace upgrade / repair even if you managed to get your hands on a Windows 8.1 ISO given that you only have a Windows 8 product key. I think that means that you only have a Windows 8 key and it's OEM, so even if the computer manufacturer had recovery media that you could purchase it would likely be "Windows 8" and not "Windows 8.1" So it came with Windows 8 pre-installed and then you upgraded to Windows 8.1. You will have to catch up your windows updates again though and I would still backup any and all critical data before hand just in case things go south. The upside is, it is generally non-destructive so you shouldn't have to reinstall all your programs, drivers, etc., etc., again. The downside is, it takes about as long as a custom clean install. If the machine boots, just insert your Windows 8.1 installation media and run setup from there and choose Upgrade. So about the only thing left to do that comes to mind short of a complete reset / reinstall of Windows 8.1 is.Īn inplace upgrade / repair which works exactly the same as it has since Vista. To repair your Windows Image and "that didn't work out"Īnd I assume you have your network adapter(s) set to obtain it's addressing schema automatically at both machines as connecting machines directly like you are doing is about the only place that APIPA actually shines. It seems to me that you've done everything I can think of.ĭism /Online /Cleanup-Image /RestoreHealth ![]() General failure." unlike just "General failure" in the cases above. When Default gateway is not defined, pinging address from another subnet like 192.168.1.1 gives "PING: transmit failed. Possibly worth noticing another thing, I'm not sure. And in these cases, the numbers of sent and received bytes do not change. In fact, I always get General failure regardless of what I ping, even 127.0.0.1. And the number of sent bytes on 192.168.10.2 grows on 42 bytes while it's 60 for received on 192.168.10.1. The interesting thing is that on 192.168.10.2 in the connection status, the number of received bytes grows about the same amount (usually the same 296 bytes though it differs sometimes) as the number of sent bytes on 192.168.10.1 the moment I ping. ![]() This connection is shown as Unidentified network on both of them. I have two laptops, one with Windows 7 and another with Windows 8.1 connected via Ethernet. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |