GLSU Excel add-in fails to load after Office update from Version 2607 to 2608
Our Excel add-in, Process Runner GLSU , fails to load after Microsoft Office updates from Version 2607 to Version 2608. This started August 17, 2026 and is actively growing in scope. Error messages: Excel: Cannot run the macro 'onLoad' VBA: System Error &H80004005 (-2147467259). Unspecified error VBA: Compile error in hidden module: ThisWorkbook Has anyone encountered similar issue with their own custom add-on. If yes, any pointers to fix it. We are seeking help on priority. Thanks, Vrushali Pawale, Sr. Manager, Insightsoftware.
Excel Protected Sheet: Cells Still Editable Even Though They Aren’t in the Unlocked Range
I’m having an issue with sheet protection in Excel where certain cells remain editable even though they are not included in any of my configured Unlocked Ranges. I have sheet protection enabled and have specifically configured the following ranges as editable: A:E G:G J:J P:BE Based on that configuration, I would expect columns F, H:I, and K:O to be protected. However, the behavior is inconsistent: Column F/G is correctly locked and cannot be edited. Columns K:O can still be edited, despite not being included in any of the Unlocked Ranges. I’m trying to understand why F/G are respecting the protection as expected while K:O remain editable under seemingly the same protection configuration.
Getting error when adding Add-ins in Excel
Hi all, I have trying to install add-ins to microsoft excel using a M365 Personal Account, and i keep getting an error "Add-in Error: We couldn't connect to the '{0}' catalog server for this add-in" screenshot attached below. I have tried on both Excel Web and and on the desktop Excel app and still the same issue, I have already had a session with microsoft support and they were not able to resolve this for me and directed me to this forum, Any help will be appreciated thanks in advance.
Office Scripts does not refresh Power BI Query live connections in Excel Online
Hello everyone, I've got the following problem and am nearly going insane because it's causing so much problems 🥲 Summary The Office Scripts method workbook.refreshAllDataConnections() no longer refreshes a live connection to a Power BI Semantic Model in Excel Online. Environment Excel Online Office Scripts Power Automate ("Recurrence" + "Run Office Script") Live connection to a Power BI Semantic Model (Analyze in Excel) Expected behavior Calling workbook.refreshAllDataConnections(); should trigger the same refresh as manually selecting Data → Refresh All in Excel Online. Actual behavior The script completes successfully without any error, but the workbook does not requery the Power BI Semantic Model. Additional observations The same workbook worked correctly for approximately two years. The issue started around mid-July 2026. Manual Data → Refresh All in Excel Online refreshes successfully. Refreshing in Excel Desktop also works correctly. The problem occurs both: when running the Office Script manually from the Automate tab in Excel Online when running the same Office Script from Power Automate ("Run Office Script") This suggests the issue is specific to the Office Scripts implementation of refreshAllDataConnections() rather than the workbook, authentication, or the Power BI connection itself. Steps to reproduce Create an Excel workbook with a live connection to a Power BI Semantic Model. Confirm that manual Data → Refresh All refreshes the data successfully. Create an Office Script containing only: function main(workbook: ExcelScript.Workbook) { // Refresh all data connections workbook.refreshAllDataConnections(); } Run the script. Result The script finishes successfully but no refresh is performed. Expected result The workbook should requery the Power BI Semantic Model exactly as when using the manual Refresh All button in Excel Online.Lambda that uses INDEX with array arguments behaves inconsistently when saved in the Name Manager
Hello, I have encountered what appears to be inconsistent behavior when a particular type of lambda is saved in the Name Manager. The issue seems to occurs when the LAMBDA uses INDEX with either the row_num or column_num argument supplied as an array. The following is a minimal reproducible example: The formula "=LAMBDA(arr,INDEX(arr,1,{1,2,4}))({1,2,3,4})" correctly evaluates to {1,2,4}. Now, save the lambda as TEST (or any other name) in the name manager. The formula "=TEST({1,2,3,4})" also spills the expected array {1,2,4}. However, when the result is passed to another function, the behavior changes. For example, "=SUM(TEST({1,2,3,4}))" and "=COLUMNS(TEST({1,2,3,4}))" both evaluate to 1. In contrast, using the lambda inline instead of the defined name produces the expected results: "=SUM(LAMBDA(arr,INDEX(arr,1,{1,2,4}))({1,2,3,4}))" returns 7, and "=COLUMNS(LAMBDA(arr,INDEX(arr,1,{1,2,4}))({1,2,3,4}))" returns 3. Unfortunately, I am unable to attach a workbook to this post. Additionally, the issue is not reproducible on every machine I have tested, although it is consistently reproducible in Excel for the Web. I am currently using Excel version 2607 on the Current Channel. Does this appear to be expected behavior, or is it a bug? In the meantime, what would be the best way to mitigate this issue? I have found two potential workarounds. The first is to prepend the result of the named lambda with a unary + (e.g "=SUM(+TEST({1,2,3,4}))"), which appears to force excel to treat the result as an array. However, when using a shared lambda library (as is the case for most of my team), users generally do not know the implementation details of each lambda, so it is difficult to determine when this workaround is necessary. The second approach is to avoid passing an array to the row_num or column_num argument of Index by using MAP. For example, the TEST lambda defined above can be rewritten as =LAMBDA(arr,MAP({1,2,4},LAMBDA(idx,INDEX(arr,1,idx)))), which causes it to behave as expected. However, I am concerned about potential performance implications. Intuitively I would expect that a single INDEX call with an array argument would be more efficient than multiple INDEX calls wrapped in MAP, but I do not know whether this is the case. Has anyone else encountered this behavior before?
Python in Excel 365 returns #CONNECT! in desktop and web
When I try to enter a simple Python expression (like "PY 1+1" ) in Excel 365 Desktop version or Web-version, I get "#Connect!" mistake in Excel Cell. When I try to run Formulas->Python->Initialization, I get error text: "Error: We weren't able to retrieve this value. We recommend restarting the external code service environment." Simple restarting Python Environment with the help of "Reset" or "Reset Runtime" do not solve the problem. I use Windows 11, Office 365 (family). PS. I would be happy if somebody could help to solve. As for now, standard Microrsoft Suport recommended to ask for a solution in TechCommunity.Microsoft.Com
Unwanted format changes on Excel worksheet in SharePoint
Hello - I've been working successfully with an Excel worksheet (.XLSX extension) that is published to SharePoint and has multiple Users viewing/updating data on this worksheet every day. Today, columns on this worksheet keep reverting back to varying widths (some way too wide and others way too narrow) despite going into the worksheet, re-formatting the column widths and saving the document. Other worksheets in the same workbook so far do not exhibit this behavior and are maintaining the desired column formatting (i.e., proper widths). I cannot figure out what is causing this unwanted formatting to happen and it has not happened before. I'm guessing this is an Excel issue, but might the SharePoint component be a factor as well? What are the potential causes of this, and what can I do to make the desired formatting remain and not revert back to the unwanted formatting? Thank you!MSO Files being randomly renamed while open on desktop
Not sure if anyone is facing this issue - but I have been facing this for 2 months now and it is really really frustating..! While working on Excel, Word or Powerpoint - a lot of times (very frequent now) the filename of the open file (on which we are working) suddenly gets saved as a random number (e.g. 12456.xlsx). If we aren't alert - if you close this file - "You lose the original file from the original location". Gone - absolutely disappears. I tried to do some research on the issue and found - Closing Excel App and reopening will give you the randomly named file in 'recent' list - however you can't open it. Checked the hidden folders and found same name file in '.temp.upload' folder, but without any .extension Renamed this file to .xslx and I got all my data back. However - if you do not rcover your file on same day there is a chance that you lose this file forever. I understand now by some online surfing that this is a Onedrive Sync issue. However, my broadband is super - checked the data throughput for the instance and it was continuous highspeed without any drops. This has become so frustrating now that I am thinking of moving out of MSO. It is very stressful and distracting now to be continuously alert and check the filename every few seconds. Does anyone else face this issue? Are there any solutions for this problem?
