User Profile
Absoblogginlutely
Iron Contributor
Joined Aug 19, 2016
User Widgets
Recent Discussions
Re: Edge Dev Version 137.0.3255.0 (64-bit) corrupted extensions
Looks like this might have been fixed in build 138.0.3309.1 that I got today. (2025.05.15) This time, clicking on repair actually did reinstall all 3 of my corrupted extensions and they are now working correctly again. Hopefully they stay fixed permanently and it's not a two day fix! Edit. 2 out of the 3 extensions are now marked as corrupt 2 hours later - obviously still not fixed :-(376Views0likes3CommentsRe: Edge Dev Version 137.0.3255.0 (64-bit) corrupted extensions
I created a new work profile and that fixed it for 5 days, but this morning after rebooting the computer I'm back to a corrupt extension in the new profile. It worked great Wednesday thru Friday. Currently running 137.0.3296.4 (Official build) dev (64-bit)211Views0likes0CommentsRe: Edge Dev Version 137.0.3255.0 (64-bit) corrupted extensions
Same issue for me on the latest version 137.0.3296.4 too. What is odd is that my personal profile is fine with the extensions and even had 2 copies of Keeper, one from the Microsoft store and one installed directly from Keeper (different versions interestingly). Attempting to repair an extension still continues to just remove the extension instead and adding new extension provides the same error I am however able to install keeper to a different work profile so it's related to my default, synched work profile account.218Views1like0CommentsRe: Edge Dev Version 137.0.3255.0 (64-bit) corrupted extensions
Same issue in that about a third of my extensions are marked as corrupt - on my local machine. Clicking on repair just removes them from the list of extensions. Same edge version. Another machine running the same edge version signed in with the same edge profile does not have the issue (at the moment). I do not have a symlink for the Dev local folder though.333Views2likes1CommentRe: Crash
Fixed with 115.0.1880.3 The browser was still on 1880.1 this morning. I went into c:\Program Files (x86)\Microsoft\EdgeUpdate and ran MicrosoftEdgeUpdate.exe -update Repeated for c:\Program Files (x86)\Microsoft\EdgeUpdate\1.3.175.27 directory. Then able to launch the browser successfully.1.9KViews0likes0CommentsRe: Crash
Jeremiah-V Same issue here. build 115.1880.1 The May Windows updates were applied this morning and Edge crashes about 3 seconds after starting. I can get to the crash page and see them all with the logs uploaded but don't have time to hit the send feedback button before the crash occurs. The startup parameters also did not fix the issue, I can get to the edge://flags/#edge-enhance-text-contrast and see it's set to default but again browser crashes before I have the chance to make any further changes. In case it helps I have webroot and keeper extensions enabled (among other's) but I would imagine those are the two big issues that could cause a problem.2KViews0likes1CommentRe: Dev channel update to 99.0.1135.5 is live
BoydB <quote>Edge Dev 99.0.1135.5 is crashing when I attempt to download a file and use the Save As button.</quote> I have the same problem with the save as dialog box crashing or hanging the machine. I initially thought it could be the upgrade to 21h2 that the pc updated to at the same time as the File/open dialog box in explorer or any other app now takes 15 seconds or more to open and populate. Also really need a way to hide the sidebar across the entire computer, and probably the entire enterprise via gpo not just the current edge profile. It was annoying turning it off on every edge profile I used.4.8KViews0likes0CommentsRe: New Feature Request - Copy Data from one profile to another within Edge
Deleted willpashley For me, I have a couple of reasons to do this. First (and most common) is creating a new profile for a new company that I'm working for - I have a common set of bookmarks for Office365/Azure that are used for every client. I also turn off saving passwords (due to using Lastpass), Turn off the option to switch profiles, Finally the profile is renamed. Using the Delegated access to Office365 is still not sufficient for day to day management, so unique profiles are created for each client (at least 34 profiles at the moment). The other scenario is when I switch from dev to beta - all my 34 profiles are no longer accessible and just copying the directories from AppData\Local\Microsoft\Edge Dev\User Data to AppData\Local\Microsoft\Edge Beta\User Data folder does not work - the new profiles do not show up. Feedback was submitted today1.9KViews0likes3CommentsRe: SharePoint Migration Tool - First Impressions
I also received the Scan File Failure:Not enough disk space to pack the file. This is using version 0.2.68.0 I have run test runs successfully on previous versions of this tool and foolishly upgraded to the latest version before attempting to go live this weekend with the full site. My previous migrations were just taking a subdirectory of my source and migrating that. The only issue I was having was the permissions getting reset on the destination sharepoint directory and locking everyone out (but easy enough to fix). My source directory is 22.3GB of content with 24gb of free space and my temp drive (which I am assume it is writing to) has 203GB free. The log file directory is being written to %appdata% which in my case is a network share if that would help diagnose the issue.10KViews1like1CommentRe: SharePoint Migration Tool - First Impressions
I saw this demo'ed at Ignite too and it looked really useful. Downloaded this afternoon and pointed it at some of our data.... My first impressions were it looked and worked nicely although could have some tweaks (see below)...Then someone pointed out they could no longer see our entire documentation library.......the permissions seemed to have been wiped. 1. It would be nice if we could migrate a subfolder of a share to a subfolder of a document site. For example migrate s:\clients\TestClientA to tenant.sharepoint.com/sharepointlibrary/TestClientA. This way it allows me to run a couple of tests up to make sure it works. Currently I can only migrate the onprem TestClientA up to tenant.sharepoint.com/sharepointlibrary/ so everything is one directory higher than it should be. In my test folder that wasn't a big deal to then select the couple of files in the root of the library and move them into TestClientA 2. Logging as mentioned goes into a random directory. Would be nice to have this linked in the gui somehow. 3. I think I lost access as the permissions on my existing share directory was for InternalDomain\UserGroup1 that does not exist in Office365 (the equivalent would be TeamTechs) (not sure why as I'm not involved in the AzureADConnect side of things) and as this does not exist in Office365 it replaced the existing permissions with a blank set of permissions as opposed to leaving the existing permissions there and still granting my TeamTechs access. 4. No smiley/sad face in the gui to add feedback information and no link to the appropriate uservoice (or other official) feedback locations. 5. I think the default option to migrate Onenote folders as a Onenote Notebook should be enabled and not turned off by default. Is there a reason this is disabled by default? On the plus side it did migrate my files across nicely and fortunately I still had access to grant permissions back to my TeamTechs group again.11KViews0likes0CommentsRe: Portal giving Bad Request error again
At last - been struggling with this for over a year. As a partner, I often get issues by logging in with a tenant id and being prompted (or worse, automatically logged into)a different tenants information. Incredibly inconvenient and a huge security issue that Microsoft seem to think is not their problem in my previous dealings with them. I found that creating a chrome user profile for each tenant and launching chrome in that user profile fixes the wrong tenant problems and I don't get cookie issues. Ideally I wanted a script that would just nuke the relevant cookies in chrome, but I was not able to work out how to do this from the command line. Doing it in the gui is several clicks and time consuming when I have to do it 15-20 times a day.7.6KViews0likes0Comments
Recent Blog Articles
No content to show