Thank you for your post.
This issue can be related to corruption or too many profiles.
If you have many unused profiles set up then it might me a good idea to delete them, to make sure any possible corruption is taken care of you may want to uninstall the current drivers and software for the wireless and reinstall the latest ones.
Corruption may occur if the drivers have been updated a couple of times while the profiles have been already available and can happen even if it is just one profile. Corruption may occur also if the profile was created on a system with different drivers than the target system. So you may want to clean install the drivers then set up the profile from this computer.
Thank you. I'll mark this answered and correct. Here's how I used your information to fix the issue:
- Only 2 profile, 1 user
- Used "Manage Wireless Networks" to delete both network profiles.
- Uninstalled wireless and wired Intel drivers
- Used Revo Uninstaller Pro to uninstall all Intel components and drivers and remove all registry items.
- Shutdown and Restart.
- Installed ProSet and wireless drivers.
- Installed wired gigabit drivers.
- Used ProSet to create the 2 profiles I need.
Again, thank you.
I was too eager to mark this closed. The problem immediately re-appeared as soon as I modified the connection properties to a fixed IP address. As I said in my original post, I use fixed IP addressing. It seems as though this is a problem for ProSet, although I'm more than willing to learn.
Next step was to open the Windows Network and Sharing Center and click on the network name select Wireless Properties and select Enable Intel Connection Settings. This allowed the use of a fixed IP address with no profile errors. Why does that not happen automatically when ProSet is installed?
I am on the verge of giving up. All methods tried so far do not survive a reboot. I worked for 6 hours yesterday with no error message. Shutdown last night, re-started this morning and got the error message after about 2 minutes. If I alter the adapter's properties to a DHCP delivered address the error goes away. But I really need to work with a fixed IP.
My have same problem too and I really need to work with a fixed IP too. Please fix this issue