User Profile
RedBeta
Iron Contributor
Joined 7 years ago
User Widgets
Recent Discussions
bad extension not identified in canary
This was a little concerning: Today I used a secondary computer (tablet) running regular MS Edge....but same extensions and synced to my PC running edge canary. One of those extensions was disabled and labeled as containing malware.....the extension had been hijacked, corrupted and discovered. It was then removed from the store. The extension was still fully functional on the canary build...Re: Error code: STATUS_BREAKPOINT
You are correct, it was a coincidence. I could not get to a github project (status_breakpoint) and then tried to go to the project community page and got the odd blank page which I had never seen before. Then checked my local dns forwarder and got the same. At the moment 121.0.2240.0 seems to be working for (status_breakpoint).Re: New tab not working in Edge Canary
It fixed it for me for one day...then it broke again. For me it happens after computer has been in sleep mode also note that ntp.msn.com responded with <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0MQsqZAAAAAAbxzPuT3UkTKl+ndlrii4BUEhMMzBFREdFMDExNgBFZGdlRe: 19603 - VPN Client Doesn't Show Domain Prefix At Bottom Anymore?
StephenWhiteD3G Yes issue is still present in 19608 and I made sure that all the components of name resolution are proper. I have veeam backups / remote desktop / WSD Samba file shares that all used to work with past builds, still work with non insider builds that require raw IPs or hosts file entries to work with the latest buildsRe: Announcing Windows 10 Insider Preview Build 19587
Ian_Salgado I just went through this problem again with 19603......you don't have Conexant HD Audio by chance? Both of my machines that have issues do....I deleted the item (device manager) with driver. On reboot It assigned the Microsoft HD Audio driver, and the update went through. With the install stuck at 62% I looked at C:\$WINDOWS.~BT\Sources\Panther\setupact.log and the last line (where it was stuck) was the Conexant HD audio line (looking for an oem cab)....maybe that will point you at what is getting stuck.
