Windows 10: strange path in Sysmon logs

Discus and support strange path in Sysmon logs in Windows 10 Network and Sharing to solve the problem; HelloIn Windows 10 Enterprise 22 H2, a strange path in TargetFilename sometimes appears in Sysmon logs:TargetFilename:... Discussion in 'Windows 10 Network and Sharing' started by Pavel Znosko, Sep 2, 2024.

  1. strange path in Sysmon logs


    HelloIn Windows 10 Enterprise 22 H2, a strange path in TargetFilename sometimes appears in Sysmon logs:TargetFilename: C:\Users\P310C~1.ZNO\AppData\Local\Temp\7b542cd6-d613-4e52-bfdf-b80fe911ff30.tmpAnd in the next event, the path is normal:TargetFilename: C:\Users\p.znosko\AppData\Local\Temp\7b542cd6-d613-4e52-bfdf-b80fe911ff30.tmpWhen I go to this directory, I will be taken to my user's folder C:\Users\p .znosko\fsutil hardlink list C:\Users\P310C~1.ZNO\NTFSLinksView.exe in C:\Users\ does not see linksI would like to understand what kind of a strange path this is C:\Users

    :)
     
    Pavel Znosko, Sep 2, 2024
    #1

  2. Sysmon DNS Query Support

    Hello,

    Welcome to Microsoft Community.

    The behavior you're encountering with the Sysmon Event ID 22 for DNS Query logs is related to how Sysmon formats its output for these events, particularly the QueryResults field. In Sysmon Event ID 22, the QueryResults field typically lists the results of the DNS query, such as IP addresses for A records, CNAME records, etc.



    Your observation concerns the absence of type: 1 in the QueryResults field, where you expect it to precede the IP addresses, indicating A records (IPv4 addresses). This formatting expectation might stem from documentation or examples that specify DNS record types explicitly in the logs.



    However, Sysmon's actual logging behavior for the QueryResults might not always include the explicit mention of type: 1 for A records. Instead, Sysmon directly lists the resolved IP addresses. The inclusion of DNS record types (like A, CNAME, MX, etc.) in the QueryResults is not a standard feature of Sysmon logging as of the versions up to my last update. The logs focus on the results of the DNS query (i.e., the IP addresses or other records resolved) without necessarily specifying the record type in a structured format like type: X.



    If you need to distinguish between different types of DNS records (A, CNAME, etc.) in your monitoring or analysis, you might have to look into additional logging solutions or DNS monitoring tools that provide more detailed information about DNS queries and responses, including explicit record types.



    Sysmon is highly customizable through its configuration, but its output format for certain types of logs, like DNS queries, is determined by the tool's internal logic and may not provide all the details you're looking for directly in the log entries. For more specific behavior or output formatting, consider supplementing Sysmon with other DNS analysis or logging tools that offer more granular insights into DNS queries and responses.

    Thank you for your patience and understanding!

    Regards,

    Manson |Microsoft Community Support Specialist
     
    Manson - MSFT, Sep 2, 2024
    #2
  3. RamAm Win User
    Sysmon Installation Confusion- Did I Get Rid of It?

    I decided to download Sysmon from here Sysmon - Sysinternals and I extracted the files into my Downloads path, just like I did with Rammap a couple months ago

    inside the folder was a EULA, Sysmon, Sysmon64, and Sysmon64a with the generic .exe logo; they belonged to www.sysinternals.com and the copyright was Mark Russinovich

    anyway, I realized Sysmon wasn't just something I could click Run as Administrator with, since it didn't work the numerous times I tried, not realizing it needed CMD, so I opted to just get rid of it, since there was also no Event Log for Sysmon in Event Viewer, under the Applications > Microsoft path

    I deleted the folder in its entirety, as well as the original zip, and even put "sysmon64 -u [force]" and "sysmon -u [force]" into CMD, but it told me that sysmon was not a recognized internal or external command, file/hash, etc.

    i then restarted my PC, there's no sysmon folder, there's no sysmon log in Event Viewer, and CMD continues to say that it doesn't exist. so am I clear of it? have I removed Sysmon from my PC? I didn't do any other commands with it in CMD other than the attempted uninstall prompt
     
    RamAm, Sep 2, 2024
    #3
  4. 1357A Win User

    strange path in Sysmon logs

    Sysmon DNS Query Support

    I have been trying to generate Sysmon Event ID 22 DNS Query logs using the below xml format

    <Sysmon schemaversion="4.90">

    <EventFiltering>

    <DnsQuery onmatch="exclude" />

    </EventFiltering>

    </Sysmon>

    But I am only able to see logs with QueryResults: type: 5 and not any other number in place of 5. Example values like type: 1, type: 2, type: 3 etc.. How do I generate logs with different numbers for type field in QueryResults? Can you let me know the xml format that can be used to generate them?


    strange path in Sysmon logs vD1lUAiJxEm%2FizEMKObWY0sgtDU8kkvdm0F1zIeUn%2F1a5SUUuvT1OTQI4lnmCYy9Prgpb3QhgOvmIVDJteaP8LQec%3D.png
     
    1357A, Sep 2, 2024
    #4
Thema:

strange path in Sysmon logs

Loading...
  1. strange path in Sysmon logs - Similar Threads - strange path Sysmon

  2. strange path in Sysmon logs

    in Windows 10 Software and Apps
    strange path in Sysmon logs: HelloIn Windows 10 Enterprise 22 H2, a strange path in TargetFilename sometimes appears in Sysmon logs:TargetFilename: C:\Users\P310C~1.ZNO\AppData\Local\Temp\7b542cd6-d613-4e52-bfdf-b80fe911ff30.tmpAnd in the next event, the path is normal:TargetFilename:...
  3. strange path in Sysmon logs

    in Windows 10 Gaming
    strange path in Sysmon logs: HelloIn Windows 10 Enterprise 22 H2, a strange path in TargetFilename sometimes appears in Sysmon logs:TargetFilename: C:\Users\P310C~1.ZNO\AppData\Local\Temp\7b542cd6-d613-4e52-bfdf-b80fe911ff30.tmpAnd in the next event, the path is normal:TargetFilename:...
  4. Powershell programming: strange behaviour with Test-Path & Resolve-Path?

    in Windows 10 Gaming
    Powershell programming: strange behaviour with Test-Path & Resolve-Path?: I have a PS script which seems to fart when testing for the existence of a certain filename. It’s the only filename it seems to have this problem on, but with all other filenames, it works as expected.Given a full pathname of the file, let’s say:Test-Path...
  5. Powershell programming: strange behaviour with Test-Path & Resolve-Path?

    in Windows 10 BSOD Crashes and Debugging
    Powershell programming: strange behaviour with Test-Path & Resolve-Path?: I have a PS script which seems to fart when testing for the existence of a certain filename. It’s the only filename it seems to have this problem on, but with all other filenames, it works as expected.Given a full pathname of the file, let’s say:Test-Path...
  6. Powershell programming: strange behaviour with Test-Path & Resolve-Path?

    in Windows 10 Software and Apps
    Powershell programming: strange behaviour with Test-Path & Resolve-Path?: I have a PS script which seems to fart when testing for the existence of a certain filename. It’s the only filename it seems to have this problem on, but with all other filenames, it works as expected.Given a full pathname of the file, let’s say:Test-Path...
  7. My path looks strange

    in Windows 10 Network and Sharing
    My path looks strange: Hi, I was wondering if my path looks correct. When I start up my laptop (Lenovo Yoga Windows 10 most recent update) I see the following path: C:\Users\User\OneDrive\Desktop\ Why do I see Users\User Does this mean I am constantly saving on OneDrive. That would be a...
  8. Sysmon update introduces DNS Query Logging

    in Windows 10 News
    Sysmon update introduces DNS Query Logging: A new version of the Sysmon tool will be released on Tuesday 11, 2019 that introduces DNS query logging to the Windows system monitor. Mike Russinovich, the creator of the tool and Microsoft Azure CTO, teased the new feature in a message on Twitter on June 8, 2019. The...
  9. Strange Log Entry

    in Windows 10 Support
    Strange Log Entry: Has anyone ever seen an entry to admin log file like this: The platform firmware has corrupted memory across the previous system power transition. Date and time: 1/11/2183 - 10:46:25 pm. How would someone even go about fixing this from reappearing since this is the third...
  10. Path to 'Documents' folder -- strange behavior

    in Windows 10 Support
    Path to 'Documents' folder -- strange behavior: About three weeks ago I migrated from XP to Windows 10, putting all my personal folders that were in XP's 'My Documents' into Win10's 'Documents' folder. The eBooks for my legacy eBook reader (MobiPocket) were in the XP folder 'My eBooks', which is now a sub-folder of Win10's...