Hi, I am really hoping someone can help me....... I have an excel spreadsheet, with a an ActiveX treeview control on it which gets loaded with child nodes when the workbook is opened. Everything was working fine till Thrusday last week, and now none of the workbooks are able to load the nodes into the treeview. We have traced the problem to the latest set of important updates KB982311, KB982308, KB982312, and KB982331 for the MS Security bulletins MS10-036 and MS10-038. Everytime we try and open the workbook a run-time error 1004 - Unable to get the Object property of the OLEObject class. Has anyone had any experience with this problem, or know of a solution to this. A little more info, is when we remove these updates then everything works fine again. Further we cannot change registry keys.... Any help with this would be brilliant....... Thanks Sak Hi sakkles - it sounds like you're running into a kill bit issue, which unfortunately would require a change to the registry. Please take a look at the blogs below and see if that helps identify the cause and the solution. This can be beneficial to other community members reading this thread. Microsoft Online Community Support Ryan, We're having the same issue. We have Excel workbooks that we distribute to our clients for the past few years. This is distributed to a variety of companies so uninstalling the update isn't a good final answer. If we reset the kill bit won't it get set back the next time an Windows update happens? We've used this control because it's on everyone's machine, it really is a 'Common Control' ; , so all we have to do is send our Excel workbook and not touch our client's image. Is there a replacement control we can use? Our environment is both WinXP Pro, Vista and Win7 with Office 2003 and Office 2007. Thanks, Paul Delke Talon Computer Associates Paul, I've done quite a bit of digging on this issue. Many of the VB6 controls were the victim of the killbit process however I think what you are seeing is a bug. From the information I've been able to gather internally the tree view control should have been patched a while back and not susceptible to the killbit in the security update. You should be able to instantiate the control. I've been able to locate at least one other case like yours. I'll post back here once I can confirm the rollup is made available. The TreeView control seems to be disabled completely. This is definitely a bug, we uninstalled all the recent updates with no results and we searched for the GUID of the TreeView control, and tried to disable the Kill-bit from registry with no success... Paul and everyone else having this issue - please download the hotfix from the following KB article which was released yesterday: Description of the Office Excel 2007 hotfix package Mso-x-none. A restart of the system may be necessary after applying this update. Will Will, I have some users who have been having the same problem. You may want to mark those controls as Safe for Initialization SFI. When you enable the content does the spreadsheet work? Take a look at this blog. It tells you how to look at the identifier for the control you are using. If the control ID matches one of those on the killbit list you will need to update it with a version of the control that is safe. Controls that are flagged as being vulnerable: File Name Control Name Class Identifier CLSID Comct232. OCX - Will Will - It is not the setting in Trust Center. All ActiveX controls are enabled. I coworker investigated the issue and found that if you uninstall the update KB982308 the TreeView control works again. For now we will uninstall this update. OCX Microsoft Windows Common Controls 6. XLS that was created prior to the KB982308 update. Our script that imports. XLS fails even with this workaround. I un-proposed that last post as an answer because while it may resolve the problem of the tree-view control not working, it also creates security vulnerabilities, which is the reason why certain controls are kill-bitted in the first place. The cause of the updated controls not working is still being investigated internally. I will post more as soon as I have any developments. Will Just a follow up to this thread. I wanted to see if everyone with this problem has applied the June update. This update fixed a problem where the treeview control showed a red X on a worksheet but worked when it was placed on a userform. Does installing this update resolve the issue of the treeview control not working? Will Thanks for trying to help Will. Our treeview has also suffered the same fate. Internally, we haven't taken the MSO updates, but our clients have, so it is causing problems. We are using Excel 2007 in XP. Installed KB983309 with no effect. Reinserted v6 of the treeview control. Works as long as I don't restart Excel. Uninstalled KB982308 and kb982133 with no effect red X still on control and method fail warning 4. Double checked that KB983309 installed 5. Tried installing v5 SP2 of the control and got a VB compile errror Proceedure Declaration does not match.... Will be nice when this problem gets fixed as it is causing us some conserable headaches. We had a very similar problem where an ActiveX control subclassing slider control stopped being instantiated when opening Excel workbook in which it was embedded. Could there be anything worse than a hacker gaining access via a security vulnerability? Perhaps Microsoft security updates that stop controls like treeview working in a spreadsheet that has been developed for a customer. The risk of a hacker accessing these vulnerabilities in a secure operating environment is surely less than Microsoft kill bits stopping functionality working before a complete fix is available!!! The latter is a sure way of causing customer dissatisfaction. I don't know how others feel but I'm becoming increasingly reluctant to apply Microsoft security updates as I've twice had to restore Windows to remove the problem on my development platform. However, that doesn't overcome the problem when the customers IT department applies the updates and then finds the spreadsheet doesn't work; it's not Microsoft who is the first to be in the firing line! Fix things properly please, don't just kill functionality until you finally get around to fixing it. Taz I've been having the same problem but with an embedded ListView object. It's been causing me a lot of grief; I've tried all of the solutions in this thread but to no avail. Can anyone suggest anything further? Have the solutions above worked for other people? Removing the security patches is working in the interim, but I need something a little more permanent. MrSkrimm's solution to update the registry worked perfectly for the Treeview issue. Now just need to figure out how to stop the expansion of all of the Treeview branches every time I save the workbook. Microsoft strikes again with KB2264403 MS10-057. If applied the treeview control will not work as my customers found out this morning. Fortunately I had prewarned them that the latest set of updates were a problem so there was no problem other than having to uninstall the update from a couple of computers. Does anyone know of a fix for this in Excel 2003 apart from uninstalling the update; is there an updated Mscomctl. Taz Hey all, Well the only way I could get around this problem with ListView anyways, I'm not using TreeView was to upgrade to Office 2007 and save the spreadsheet as a macro enabled spreadsheet. Miraculously worked after that so I didnt look into it any further. Isn't that convenient, only way to fix a problem caused by Microsoft is to pay them for a new version of the software... I converted the excel file in 2007, I still have the same problem: ListView that is displayed with red crosses and the application does not work... The elements just appear with a red cross since the security update. My System consists of WinXP and Office 2003 SP3 with all the security updates because of company policy. I can use the treeview like before the update.. Hi all, we are having the same problems on several Windows XP machines with Office2007 installed. Strangely enough, on some it works, on some it does not. I just tried MrSkimms fix on a developer machine and it seems to work; however I will give it another try on the user machines and keep you posted. Still: Thank you MrSkimm! Regards, Ralph Regards, Ralph.
