Win 10 corrupted by Win 7 program that runs correctly there!
-
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP. When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible). See Bad Start Menu[^] There are lots of error entries in the Event Log like: EventLog Example 1[^] EventLog Example 2[^] EventLog Example 3[^] EventLog Example 4[^] The program, itself, seems to operate correctly!!! Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10. To my surprise, the symptoms were the same! :omg: (I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.) For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications. I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why. Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" ;-) to use, etc? Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be
-
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP. When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible). See Bad Start Menu[^] There are lots of error entries in the Event Log like: EventLog Example 1[^] EventLog Example 2[^] EventLog Example 3[^] EventLog Example 4[^] The program, itself, seems to operate correctly!!! Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10. To my surprise, the symptoms were the same! :omg: (I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.) For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications. I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why. Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" ;-) to use, etc? Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be
Matt T Heffron wrote:
but with right mouse click a simplified, text only menu appears
That is exactly what one expects to see with right-click on the start button. What do you actually see on a left click? As to the event log entries, how do they relate to your application?
-
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP. When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible). See Bad Start Menu[^] There are lots of error entries in the Event Log like: EventLog Example 1[^] EventLog Example 2[^] EventLog Example 3[^] EventLog Example 4[^] The program, itself, seems to operate correctly!!! Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10. To my surprise, the symptoms were the same! :omg: (I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.) For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications. I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why. Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" ;-) to use, etc? Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be
The event log entries suggest that your DCOM permissions are broken:
Error message when you try to view certain Windows Server 2003 components and snap-ins: "error code 80040153 - Invalid value for registry"[^]:
When this issue occurs, error events that resemble one or more of the following may be logged in the System log: Event ID 10022 Source: COM Description: The machine-default access security descriptor for the COM Server application D:\exchsrvr\bin\mad.exe is invalid. It contains access control entries with permissions that are invalid. This security permission can be corrected using the Component Services administrative tool.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Matt T Heffron wrote:
but with right mouse click a simplified, text only menu appears
That is exactly what one expects to see with right-click on the start button. What do you actually see on a left click? As to the event log entries, how do they relate to your application?
Left click does nothing at all. (I had never done right click on the Win 10 start button!) Some of the menu items also do nothing when clicked.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed." - G.K. Chesterton
-
The event log entries suggest that your DCOM permissions are broken:
Error message when you try to view certain Windows Server 2003 components and snap-ins: "error code 80040153 - Invalid value for registry"[^]:
When this issue occurs, error events that resemble one or more of the following may be logged in the System log: Event ID 10022 Source: COM Description: The machine-default access security descriptor for the COM Server application D:\exchsrvr\bin\mad.exe is invalid. It contains access control entries with permissions that are invalid. This security permission can be corrected using the Component Services administrative tool.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Thanks! So the next question will be: How do I figure out what part of the program installation wreaks havoc with the DCOM permissions in such a way as to have no (apparent) effect on a Windows 7 system, but is a disaster when upgrading to Windows 10? (And clobbers Windows 10 directly, when installed onto Windows 10.)
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed." - G.K. Chesterton
-
Thanks! So the next question will be: How do I figure out what part of the program installation wreaks havoc with the DCOM permissions in such a way as to have no (apparent) effect on a Windows 7 system, but is a disaster when upgrading to Windows 10? (And clobbers Windows 10 directly, when installed onto Windows 10.)
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed." - G.K. Chesterton
This sort of problem is going to be painful to diagnose. I'd suggest:
- Start with a fresh Win7 VM;
- Open
dcomcnfg, and look at the various settings under "My Computer ⇒ Properties ⇒ COM Security"; - Install the application;
- Look at the COM Security settings again, and try to work out what's changed;
- Upgrade to Win10;
- Look at the COM Security settings again, and compare to the values from before the upgrade; (You might need to do this from a remote PC if you can't open
dcomcnfgon the upgraded box.)
Alternatively, you could use something like Process Monitor[^] to monitor the installation to see what it's doing.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP. When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible). See Bad Start Menu[^] There are lots of error entries in the Event Log like: EventLog Example 1[^] EventLog Example 2[^] EventLog Example 3[^] EventLog Example 4[^] The program, itself, seems to operate correctly!!! Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10. To my surprise, the symptoms were the same! :omg: (I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.) For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications. I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why. Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" ;-) to use, etc? Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be
This is a "3rd party" product that you do not have the source to? Not worth the trouble, IMO. It could be anything, starting with Windows Update reversing every "retro" driver update you might make when you're not watching. I remember one upgrade in particular ... Robotron 2084 "over-clocked" and became unplayable. Sad.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
This is a "3rd party" product that you do not have the source to? Not worth the trouble, IMO. It could be anything, starting with Windows Update reversing every "retro" driver update you might make when you're not watching. I remember one upgrade in particular ... Robotron 2084 "over-clocked" and became unplayable. Sad.
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
This is a "3rd party" product that we OEM as part of some of our products. (Much "core" functionality, not just an added-on library/control.) We have recently licensed the source, but the installer is using a very old version of InstallShield. (XP-era) Modifying the installer to work with Windows 10 is another project. I'm just trying to figure out how to upgrade my development laptop, that already has this product installed, from Windows 7 to Windows 10, without getting the corruption I've seen. (Secondarily, knowing this would be useful in case a customer wants to do the same upgrade.)
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed." - G.K. Chesterton
-
This is a "3rd party" product that we OEM as part of some of our products. (Much "core" functionality, not just an added-on library/control.) We have recently licensed the source, but the installer is using a very old version of InstallShield. (XP-era) Modifying the installer to work with Windows 10 is another project. I'm just trying to figure out how to upgrade my development laptop, that already has this product installed, from Windows 7 to Windows 10, without getting the corruption I've seen. (Secondarily, knowing this would be useful in case a customer wants to do the same upgrade.)
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be killed." - G.K. Chesterton
Some older programs try to force Windows "Classic" mode; that will do weird things. Some programs must compile to x86 (for 64); cannot run mixed. Inno setup handles all my setups; x86 / 64; EF; SQL Server. (XP; 7; 8.1; 10). I would "move" the project to a Windows 10 machine; not go Win 7 to 10 with the project on the machine. (XP was always nice ... by itself). (The most I usually do for any machine is upgrade from "home" to "pro". After that, it's a new machine). (I've developed on 8.1; for 7; that runs on 10; VM Box good; Hyper-V not so much - screen artifacts).
"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal
-
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP. When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible). See Bad Start Menu[^] There are lots of error entries in the Event Log like: EventLog Example 1[^] EventLog Example 2[^] EventLog Example 3[^] EventLog Example 4[^] The program, itself, seems to operate correctly!!! Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10. To my surprise, the symptoms were the same! :omg: (I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.) For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications. I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why. Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" ;-) to use, etc? Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be
Windows OS ISO Download Index - TechAbby[^] you can easily download windows ISO from here for free
-
I have a Windows 7 program that works fine in Windows 7 (32 or 64), and has been working since Windows XP. When it is installed on a Windows 10 64-bit system (or VM) the Windows 10 system is substantially corrupted. For example, the "start menu" won't open with left mouse click, but with right mouse click a simplified, text only menu appears, and most of the menu entries fail to do anything (visible). See Bad Start Menu[^] There are lots of error entries in the Event Log like: EventLog Example 1[^] EventLog Example 2[^] EventLog Example 3[^] EventLog Example 4[^] The program, itself, seems to operate correctly!!! Since the installer is quite old I suspected that was the culprit. I tried setting up a VM with Windows 7 64-bit and installed the program. Then I used the "standard" Microsoft upgrade to Windows 10. To my surprise, the symptoms were the same! :omg: (I was sure to check the start menu immediately after the upgrade, before the program was run and could cause the errors itself.) For ongoing legacy software support, my primary development system at work is still Windows 7 64-bit. There's now a lot of pressure to upgrade the system to Windows 10, but I don't want to do that if it'll end up corrupted. And I'd rather not have the system re-imaged to Windows 10 and need to reinstall all my applications. I'm afraid that's where this will end up, but there may be some customers who try to upgrade (because their IT department says they must), so I think it's important to know what's going on, and why. Does anyone have any thoughts on the root cause, how to diagnose this, the appropriate "Google foo" ;-) to use, etc? Thanks.
"Fairy tales do not tell children the dragons exist. Children already know that dragons exist. Fairy tales tell children the dragons can be
m also searching check out this [url=adeleweightloss.com/keto-slim-diet-reviews/] adeleweightloss.com/keto-slim-diet-reviews/ [/url]
-
Windows OS ISO Download Index - TechAbby[^] you can easily download windows ISO from here for free
