1226. Coplilot Workflow Tips

 

Copilot Workflow Tip for Reliable Archiving and Research

If you're building a robust archive of troubleshooting steps, historical research, or technical workflows, here’s how to make the most of Copilot:

✅ Use the Copilot mobile or desktop app for long sessions

• These platforms offer better chat history visibility, session continuity, and memory features.

• Ideal for multi-hour deep dives or ongoing research threads.

📌 Bookmark key chats or use Copilot Pages

• Pages let you preserve, organize, and edit long-form content side by side with Copilot.

• You can turn any chat into a page by hovering over a message and selecting “Edit in a page”.

• Great for saving solutions, timelines, or structured notes.

🔐 Always sign in before starting major troubleshooting or research

• Signing in ensures your conversations are saved to your account.

• Anonymous sessions are stored locally and cannot be recovered once you sign in or switch devices.

----------------------------------------------------------------------------------------------

When you simply search Google/Bing and get the AI response, do not Dive Down for more becasue you will be Anonymous and conversation will not be kept in Microsoft account. If you forget, you can always do a COPY/PASTE of conversation into your own PC file. But, if you want it to be kept and managed by Microsoft account, use the App as explained above..

1225. How I Solved the 0x80070035 Error After Renaming My PCs — The Real Fix Microsoft Missed

 

🛠️ How I Solved the 0x80070035 Error After Renaming My PCs — The Real Fix Microsoft Missed

For six months, I struggled with a persistent Windows error: “0x80070035 – Network path not found” It blocked file sharing between two PCs on my private network. Sometimes the other PC would appear in File Explorer, sometimes not. But even when it did, trying to access shared folders failed every time.

I tried everything:

• Network discovery settings

• SMB protocol tweaks

• Firewall rules

• IP-based access

• DNS flushes and Winsock resets

Nothing worked. Until I discovered the real culprit — and it’s one Microsoft never warns you about.

🧨 The Hidden Problem: Stale Credentials After Renaming PCs

Months ago, I renamed both PCs. What I didn’t realize is that Windows Credential Manager still stored credentials tied to the old PC names, even though the IP addresses stayed the same.

This created a silent conflict:

• File Explorer resolved the new name to the correct IP.

• But authentication failed because the stored credentials referenced the old name at that same IP.

• Result: 0x80070035 every time.

✅ The Real Fix: Clean Up Windows Credentials

Here’s how I solved it in minutes — after six hours of wasted troubleshooting:

1. Open Credential Manager

• Press Windows + S and search for Credential Manager

• Go to Windows Credentials

2. Remove Old PC Name Entries

• Look for entries like TERMSRV/Old-PC-Name or Old-PC-Name

• Delete any credentials tied to the old computer names

3. Add New Credentials

• Click Add a Windows credential

• Enter:

  • Network address: \\New-PC-Name or its IP (e.g., \\192.168.1.10)

  • Username: The account name on the target PC

  • Password: The password for that account

4. Repeat on Both PCs

• Do the same cleanup and re-entry on each PC involved in sharing

5. Test Access

• Open File Explorer and enter \\New-PC-Name or \\192.168.1.x

• Shared folders should now appear without error

🧠 Why Microsoft Doesn’t Fix This Automatically

Renaming a PC does not update stored credentials. Windows assumes manual management, which leads to silent conflicts when:

• The IP stays the same

• The name changes

• The old credentials remain active

🧭 Final Notes

• You don’t need static IPs or hosts file edits unless you’re deliberately changing addresses.

• The only real fix is cleaning up Credential Manager.

• If you’ve renamed a PC and lost access to shared folders, this is the first thing to check.

If you’ve hit this wall like I did, I hope this saves you hours — or months — of frustration. Feel free to share or repost. This fix deserves to be known.

1224. Prevent future FEATURES updates and notification

 Preventing future feature updates in Windows is possible using several methods, although it is generally not recommended due to the security vulnerabilities that can arise from running outdated software.

For all Windows editions, the Registry Editor (regedit) can be used, though caution is advised. After backing up the registry, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows, create a new key named WindowsUpdate, and inside that, create another key named AU. In the AU key, create a new DWORD (32-bit) Value named NoAutoUpdate and set its value to 1. A restart is required. 

Another approach involves disabling the Windows Update Service through the Services app (services.msc) by changing the Startup type to Disabled and stopping the service. However, Windows may attempt to re-enable it. 

For Windows 10/11 Home users, setting your network connection as metered in Settings can help prevent automatic updates. 

1223. Change AT&T DNS Addresses due to problems

 For several days we had constant problems with Amazon and FamilySearch websites. Most of the time they came up, but when they did certain subsequent events did not, e.g. could not display books on Amazon, or get to records on Family Search. Both sites reported problems, so AT7T network didn't seem like an issue. Wrong. 

The overall performance also was intermittently lagging. So, I focused on the DNS Servers, which both of those sites may have also used, and asked if they could be changed since Internet AI was insistent with NO! Wrong again!

They can be changed. I would do this in the past for the ipV4 protocol. At that time, aging myself, ipV6 had so many problems that it was recommended to turn it off. Well, now it's become the standard and used to address the exponential increase in IP addresses (smartphones, etc.). Of course the formats from ipV4 were changed for the DNS addresses, so I needed to know alternatives for AT&T DNS server addresses.

The defaults for AT&T ipV6 are:

2600:1702:3b20:11b0::42  (primary) and

2600:1702:3b20:a1b0:10ed:bccb:e63a:b684  (alternate)

Its DNS Servers are:

2600:1702:3b20:11b0::1    (primary)

Instead, I changed the DNS Server to Googles addresses:

2001:4860:4860::8888  and 2001:4860:4860::8844 which resulted in

2001:4860:4860::8888 converting to 2001:4860:4860::808:808 and

2001:4860:4860::8844 converting to 2001:4860:4860::808:404

Mystery to me what all the numbers mean -- will look up some time. But for now they resolved ALL DNS issues immediately.

Now, how did I change them?

Network & Internet Center > Look at your Wi-Fi active connection and Properties

Select "Change DNS settings for all Wi-Fi networks"

Select "EDIT"

Then :Edit Network Settings and pull down "AUTO DHCP"

Slect "Manual"

Set IpV6 to ON

Now enter the preferred addresses for Google above

Then Reconnect your Wifi which was disconnected automatically

Enter your Password for your Wi-Fi.

Note: I had to figure out the steps from older steps which no longer worked and you might have to do the same from mine.