New Problem with later Windows 10

[[email protected]]

I use only TCC which I generally start from an icon on the desktop. I have observed a new problem with the last few versions of Win10 that I have installed. I am on the Fast Ring of the Windows Insider program and on the last couple of versions of Win10 (currently 18945), the first time I start TCC from the icon the screen comes up as a dud i.e. there is the normal heading and then nothing---there is no disk called out. In the Task Bar it has a funny thing rather than the usual "Admin: TCC". You can't do anything on that instantiation except kill it. This is not a major problem, but it is annoying. In 4start.cmd I have prompt "`%@lower[%_disk]`:$g" so normally I would get a prompt like "c:>", but no joy.

 

[rconn]

Not reproducible here on two systems running 18945. (The third system hangs repeatedly during the update process, so I don't have a lot of confidence in 18945 …)

Are you running any plugins? Did you try it w/o TCMD.INI?

 

[[email protected]]

No, I am using 4start.cmd, a carryover from long ago. I have, hopefully, attached a copy below.

 

[[email protected]]

Hmm, I reread that and as far as I know I am not using tcmd.ini.

 

[vefatica]

Hmm, I reread that and as far as I know I am not using tcmd.ini.

I think you MUST be using TCMD.INI unless you specifically start TCC with the "/ii" option.

 

[vefatica]

Which TCLOCK do you use?

 

[[email protected]]

The version of TCLOCK that I am using is marked T-Clock Redux x64 - Build 2.4.4 Build 492.

 

[[email protected]]

Yeah, I guess that I am using TCMD.INI. It is attached below, I hope.

 

[[email protected]]

HELP!!! It is still doing it!!! I must discard the first instantiation of TCC after a reboot. This is REALLY annoying! My current version of Windows 10 is Version 10.0.18956.1000. HELP!!!

 

[rconn]

It's still not reproducible here. I'm running four systems with the latest Win 10 insider build (fast ring), with no issues.

Anybody else seeing this?

 

[[email protected]]

O.K. It goes as follows: I use only TCC and i call it from a desktop icon. It is set to Run as Administrator. When I reboot Windows, I call TCC and the first instantiation has no prompt - just a blank screen after the header. Oh, my prompt is set to C:. If I kill that instantiation of TCC, from then on it works fine with additional instantiations of TCC. I generally have four TCC instantiations at all times. This is not game-changing, but it is EXTREMELY annoying.