Stubborn APIPA Issue (possible IPv4 problem, IPv6 = okay?)

Question

I have one Windows 7 desktop that seems to be stuck on an APIPA address. It can see the other computers in the workgroup, but seemingly only communicate via IPv6 (see below), and can't access outside the LAN. The problem began today after completing a Windows update. Troubleshooting so far has already included:

-Ipconfig release/renew
-Uninstalling/reinstalling the NIC driver
-Checking device manager for "hidden" NIC drivers (none)
-Flushing DNS and ARP
-Resetting winsock and ipv4 using netsh
-Manually assigning an IP address on my subnet
-Doing a system restore to before the Windows update
-Restarting DHCP client service
-Disabling Windows Firewall
-Unloading TrendMicro
-Malware Bytes scan

I tried unplugging the ethernet cable from that PC and putting it in a laptop and it connected fine, got a proper IP, and connected to the internet (yes, I disabled WiFi on the laptop before testing).

Currently, when I try to ping another legitimate address on the network or the router (192.168.0.1), I'm getting:

PING: transmit failed. General failure.

Interestingly, when I ping the NetBIOS name of another host, it works, but it is running the ping over IPv6.

I then tried to ping -4 [host name], which returned:

Ping request could not find host [host name]. 

Also, an ipconfig/release returns this:

An error occurred while releasing interface Local Area Connection : An address has not yet been associated with the network endpoint.

An error occurred while releasing interface Loopback Pseudo-Interface : The system cannot find the file specified. 

I am stumped! I hope somebody has a suggestion short of a fresh Windows install or replacing the NIC.

Solution 1

Well I left MalwareBytes "Full Scan" running over night and when I returned in the morning there was one infected file "Backdoor.bot" that the "Quick Scan" didn't pick up. As soon as I cleaned it the problem resolved itself.

Solution 2

In order to resolve APIPA first run cmd prompt in admin mode and do the following:
^{Note: if you dont run the cmd in admin mode, it wont work.}

netsh winsock reset all 

netsh int ip reset all

After this, you'll have to restart the computer. Do not attempt to open a browser or whatsoever.

Once the computer has restarted it should work