|
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
modified 8-Mar-18 15:53pm.
|
|
|
|
|
The event log entries suggest that your DCOM permissions are broken:
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
|
|
|
|
|
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 dcomcnfg on 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
|
|
|
|
|
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
|
|
|
|
|
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
modified 9-Mar-18 21:49pm.
|
|
|
|
|
Redirects to spam.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I need to create a self-signed certificate and private key on a new installed win7x64 sp1. For this, I installed the Windows SDK and Driver Kit 7.1.0 updated the framework to 4.5. Then, according to the instructions, I need to execute the first command on the command line - "cd C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin" then run the second command - "makecert -r -sv C:\WinItProDriverCert\WinitproDrivers.pvk -n CN="Winitpro" C:\WinItProDriverCert\WinItProDrivers.cer" But when I try to run the second command, I get an error :
"" Error: Unable to create file for the subject <' C:\WinItProFriverCert\WinItProFrivers.pvk'"
Error: Can't create the key of the subject <' C:\WinItProFriverCert\WinItProFrivers.pvk'"
Failed ""
|
|
|
|
|
Does that folder exist?
Do you have permission to write to it?
Are you running the command from an elevated command-prompt?
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Try to open the command prompt as run by an administrator. many of the users do not do that and then get the error on the second stage. As I have also tried this and this helped in the second stage and google support number had helped me a lot with this.
|
|
|
|
|
Procedure to replicate this astonishing behavior:
1. Windows search using " *.* AND Kind: Folder " on LocalDisk (of total size 1.81 TB as reported)
2. After search returns all folders (oddly, the above quoted string returns "file" as well), select all in window and right-click "Properties".
3. Wait for tally to finish.
As mentioned not only is "File" tally rolled up but, in any specific file count returnn on any system where files might occupy any percentage of free space (I'd imagine, anyway), the count is way too high.
This seems weird to me.
|
|
|
|
|
Junctions / reparse points?
Hard Links and Junctions (Windows)[^]
Since Vista, there's a junction called "C:\Documents and Settings" which points to the "C:\Users" folder. There's a symbolic link from "C:\Users\All Users" to "C:\ProgramData", and one from "C:\Users\Default User" to "C:\Users\Default". There are various others within each user profile. These were added so that programs which used hard-coded paths wouldn't break when the folders were reorganised to make the full paths shorter.
Some applications - possibly including Windows Explorer - don't understand these links, and will list the files from both the original location and the junction.
For example, "C:\ProgramData\test.txt" could be listed as:
- "C:\ProgramData\test.txt"
- "C:\Users\All Users\test.txt"
- "C:\Documents and Settings\All Users\test.txt"
With nested junctions, the number of times the same file can be listed will grow dramatically.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Ok, yeah.
Like Windows' ability to unzip a .zip file and either report the subfile/subfolder as an entity.
So essentially this explanation can account for overstated file count and size.
But what about the fact the search is specifically FOLDER but it returns FILE count?
Just seems odd to me.
Thanks.
|
|
|
|
|
The search is returning the folders, but when you view the properties, the property dialog also counts the files within those folders. That's just how Windows Explorer works.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Hi guys,
I've got an MFC program that I've been developing for, well, since Windows 2000. We heavily leverage threads in this app - multiple background worker threads at a low priority, a rendering thread at a higher (but still below-normal) priority, then the main threads at a regular priority for the app to remain responsive to the user interaction with the GUI.
It's worked great for W2K, WinXP, Vista, 7, and even 8 along with various flavour of each (though I didn't test much in Win 8). Now, with Win10, the GUI and in fact the entire operating system seems to be lethargic when the low priority threads are working - appearing to defeat the purpose of setting thread priorities.
My threading library code hasn't changed, only the OS. And if I take the current build and run it on Win7, it behaves as expected. I've done a cursory review and can't find what's changed in the API to correct this. Did Microsoft change/break basic thread priorities in Windows 10, or am I missing something else?
Thanks,
--Rob
|
|
|
|
|
Did you ever resolve this? I'd be interested in the solution. 
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Double-clicking an image file in Windows (File) Explorer in Windows 10 ... how can I get this to open in a program of my choice? Going through the Settings, either default programs or file associations makes no difference.... I've Googled this and found no solution. Anyone here have one?
|
|
|
|
|
Right click, choose properties. Use the Change button near the "Opens with" box.
|
|
|
|
|
Thanks - yes it works now. I was confused by my alternate File Explorer s/w (Directory Opus) which was hijacking things. Looks like I was blaming Windows unfairly.....
|
|
|
|
|
A_Griffin wrote: Looks like I was blaming Windows unfairly.
Something we all do from time to time.
|
|
|
|
|
i want to format my laptop from windows 10 to ubunto , but i want to format just disk C and keeping all my E disk files , is it possible doing that while changing to ubunto and having access to them there ? and vise versa if i want to go back to windows could i keep some files ...
|
|
|
|
|
Yes; I've got Windows 7 on my SSD (my C drive), and installed Ubuntu on an external USB-drive (with a bootloader on the C drive). That way I can choose during booting which OS I would like to boot.
I can access the Windows-files from Ubuntu without problems, but not the other way around; Windows does not recognize the format of the Ubuntu-partition and suggests that it will need formatting.
If you want to try it first (without installing) than that is possible too. Go to Boot and run Linux from a USB flash memory stick | USB Pen Drive Linux[^] and download an installer. You can than run the OS you choose from USB, and if you like it, install it from USB.
Once installed, you'll probably also be wanting to install "Wine". With Wine you can run some Windows-software on Ubuntu. Notepad++ and WarCraft should work, Visual Studio doesn't.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
This is not a question - I just need to get some frustration out. And as a warning to other people about the problem.
I have this utility generating a batch file for setting environment variable values. (The need arises because under the Bamboo build system, any environment setting is lost from one job step to the next; each job step must set the environment variables anew - but this is of minor importance to the problem). PATH and SET commands are written to a file named on the command line - I usually name it setenv.bat - and then executed in every job step.
Only that some users, running this utility on their desktop machines, ended up with crazy environment settings, not at all those that the utility shold have generated. But the debugger showed the correct commands to be written to the file. The .bat file appeared to, in mysterious ways, being modified between being written and being executed on the next command line.
The problem occured on PCs running cmd.exe in the default working directory, that of cmd.exe itself - C:\Windows\System32. (Most users change the CWD of cmd.exe to C:\ or some project directory, but those who rarely use CLI systems may not care to.) Running the utility from any other directory worked fine, but not from C:\Windows\System32. setenv.bat was not written to the directory; it never appeared.
I suspected access right problems, but creating the file caused no error/exception. Maybe the physical file was not accessed (causing the exception) until the file was flushed? So I flushed the file explicitly before closing it. Still no exception.
After closing I checked for File.Exists("C:\Windows\System32\setenv.bat"). True - file exists. I tried to open it: Once again - successful. I could read the correctly written contents. The file was completely absent from C:\Windows\System32\, yet I could create it, write to it, close it, open it again and read C:\Windows\System32\setenv.bat... What the... ???
So I searched the entire file system for the file setenv.bat. The first occurence explained how the crazy, incorrect settings could be made: Some completely unreated job had left a setenv.bat file in a directory on the path. Then there was a second setenv.bat occurence: In C:\Windows\SysWOW64, with a last written time stamp revealing that is was our guy.
I haven't yet sat down to learn the relationhship between System32 and SysWOW64 (but I sure will do now!). Appearently, System32 is interpreted as one core set of files, plus some extra - but the extras depend on who is asking. When a .net application (such as my utilitiy) asks, it gets the core+extras named SysWOW64, and new files are written to the extra part. When Explorer asks, it gets the core + another set of extras which do not overlap the extras of SysWOW64. When cmd.exe asks, in spite of being located in System32, does not get the SysWOW64 extras, but the same extras as Explorer. (Is it not a 32 bit program, in spite of its location?).
A simple workaround is to write to .\setenv.bat rather than setenv.bat. Even though CWD is identical in my utility and in cmd.exe, the .\setenv.bat generated is distinct from the .\setenv.bat executed on the next line. You then get an error message because C:\Windows\System32\setenv.bat, in the cmd.exe understanding, isn't there. But my utility cannot tell you in advance - to it, C:\Windows\System32\setenv.bat IS there!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
