VB6 Application on Windows 10 Creators Update does not run
Since Windows 10 Creators Update we are facing problems with an VB6 Application which does not run anymore. The application is starting and is ending in a part of a second. We found out that several person are facing the same problem due to a function "MKDIR" in VB6. We tried it out but that was not the reason in our environment. We do not have this problem with a former built of Windows 10.
Does soembody has an idea?
Thanks.
Does soembody has an idea?
Thanks.
David Johnson, CD
where are you trying to make the directory?
ASKER
in C:\Temp but we removed the command without any improvements.
Use FileMon to track down issues of this kind.
As you mentioned C:\Temp.. normal users have only read permissions on C:\. This is the default since years. Thus you cannot expect MkDir to work at all.
And there more locations, where a normal user cannot write to..
As you mentioned C:\Temp.. normal users have only read permissions on C:\. This is the default since years. Thus you cannot expect MkDir to work at all.
And there more locations, where a normal user cannot write to..
@ste5an
Don't confuse permissions on the root of c: with perms on subfolders of c:. By default, users may create subfolders and do everything they like in these.
Don't confuse permissions on the root of c: with perms on subfolders of c:. By default, users may create subfolders and do everything they like in these.
I don't. But users have per default only read & execute on C: (root). Thus they cannot create a directory. Thus MkDir "C:\Temp" must fail.
Further more, when Temp is not created properly, then users still have no write or create permissions in C:\Temp..
And no: normal users have not the permission to create folders in C:\ (root).
Further more, when Temp is not created properly, then users still have no write or create permissions in C:\Temp..
And no: normal users have not the permission to create folders in C:\ (root).
"Thus they cannot create a directory" - wrong. Try it, take a clean system and you'll see.
It's not about this concrete setup. Its about the default permissions on file systems as stated by MS.. I don't have the link at hand, but I will look for it later.
My stars... non-admins may not write to c: since winxp - correct, but they can still create folders on c: - preventing that is a measure that we have incorporated using GPOs since 10 years. The default ACLs do not disallow that, no.
ASKER
I removed the MKDIR command but still the same problem. I'll try to use Filemon as Ste5an mentioned before...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Max555, you need to close the question now by selecting your last comment as answer.
ASKER
Found out the solution