Windows 10: My computer cant't get through log in session

Hello, im having an issue with boot or login problem with my optiplex 9010 dell computer. I was playing then suddenly it shut down and after that i tried to log on to my computer the usual way i does it wouldnt go through the log in session and sometime i got the "it look like window didnt load correctly". I have tried alot of ways but none of it fix my problem, please help me.i tried to insert image but it didnt go through

:)

 

Shutdown or Log off in a Citrix Windows 10 VDI session

Hi Community gurus,

Hoping you could advise. During the outbreak, most of my teams are working from home and being offered a Windows 10 VDI remote login on Citrix server. In my organisation, there is a token limit and therefore we are not allowed to stay in the session
for too long but only carry out time card logging routine which takes about 5 - 10 minutes depending on individual operations. People who have logged in for prolong period get reported to their mangers who then advise to shorten the session as much as they
can.

Some of them did get reported but mainly was because they did not disconnect the session properly, and still wondered how to disconnect the session properly without occupying the server resources.

Luckily I have never been in the list, and helped myself a quick short which runs "shutdown.exe -s -f -t 0".

This has run perfectly and my Manger did notice I was never in the reporting list and wondered how I did it.

Therefore I shared with my team with this quick shortcut, however, one of my seniors suggested that it's betters to use shutdown.exe -l -f 0

To me, his advice was to log off the session, instead of shutting down, but I wondered that in a shared virtual machine session(s), is there really difference on log off and shutdown as the shutdown command does not appear to shut the server down, but disconnecting
my session so that others have more resources when needed.

Would any one be able to advise?

Thank you in advance.

 

Remote desktop sessions

Hi,



Thank you for writing to Microsoft Community Forums.

I understand how difficult it can be when the feature does not work the way it is supposed to. However, you can go ahead and try these steps and let us know the status.

1. Remove your network cable, or turn off your Wi-Fi.
   
2. Reboot your computer
   
3. Login to your computer, without the network plugged in.
   
4. Once you are logged in, plug in your network cable or turn your Wi-Fi back on.
   
5. Check if you get the same issue.
   

However, if the issue is still persist for your RDP session in Windows server 2016, I would suggest you to post your query in
TechNet forums,
where we have the engineers with the expertise to provide solutions for issues related to Windows server 2016.



Aditya Roy

Microsoft Community – Moderator

 

"Public CBS Session Leak Detected" in CBS Logs- What Does it Mean?

Hello, JamesBacon620

Welcome to Microsoft Community.

In the context of CBS (Component-Based Servicing) logs in Windows, the message "Public CBS Session Leak Detected" typically indicates a problem related to the management of system resources, specifically with sessions and objects. Here's what the information in your log entry means:

1. Public CBS Session Leak Detected: This message suggests that the Component-Based Servicing system has identified a situation where a session has not been closed or released properly. CBS manages various components and updates in Windows, and sessions are used to keep track of these operations.
   
2. Session ID: The "Session ID" mentioned in the log entry is a unique identifier associated with a specific operation or task in CBS. It helps CBS track and manage the components and updates being installed or modified.
   
3. Clients (FodHelper and SystemSettings): These are the components or applications that were involved in the session that experienced the leak. In your log entry, FodHelper (LanguageFeaturesOnDemand) and SystemSettings are identified as the clients responsible for this issue.
   
4. Reference Count: The reference count indicates how many references or instances of a particular object or session are active. In your log entry, it mentions a reference count of 6 for both clients, which suggests that there were six references to these sessions when there should have been none or fewer.
   
5. HRESULT Codes: The HRESULT (Handle to Result) codes are error codes that provide more information about the nature of the problem. In your log entry, the HRESULT codes (0x880f0909 and 0x888f0909) indicate that a public object leak occurred.
   

Generally, "Session Leaks" like the one mentioned in your logs can be indicative of a problem with system resource management, but they don't necessarily mean that there's a security threat or malware present. These leaks can potentially lead to system instability or performance issues over time if they accumulate.

Overall, this is a normal report and CBS.log will only record updates to these system components and resources. These Objects are just resources from the application or system performance. It does not involve personal privacy information on your PC. Do not worry

Hope it helps! If any update, welcome to share with us.

Best regards,



Chandy |Microsoft Community Support Specialist