Quantcast
Channel: Sysinternals Forums
Viewing all 10386 articles
Browse latest View live
↧

PsTools : Psexec - process exited with error

April 15, 2018, 10:20 pm
$
0
0
Author: Aditza
Subject: Psexec - process exited with error
Posted: 16 April 2018 at 5:20am

update: just tested it, KB4101864 does indeed fix the ntfs acl error message "This security ID may not be assigned as the owner of this object" that appears when the user tries to create a new file, has full access rights but is not the owner of the folder.


Edited by Aditza - 1 hour 11 minutes ago at 5:44am
↧
Search

Autoruns : Remove "File not Found"

April 16, 2018, 5:14 am
$
0
0
Author: ken1943
Subject: Remove "File not Found"
Posted: 16 April 2018 at 12:14pm

I do not remember when, but there was a reason to not remove 'file not found'. Been years since I stopped deleting them.
↧
↧

PsTools : Psexec - process exited with error

April 16, 2018, 5:36 pm
$
0
0
Author: dexter
Subject: Psexec - process exited with error
Posted: 17 April 2018 at 12:36am

Thank you Aditza. I will try the update.
↧

Site Bugs : ACTION REQUIRED - Migration to Technet Forums

April 16, 2018, 6:55 pm
$
0
0
Author: lukim
Subject: ACTION REQUIRED - Migration to Technet Forums
Posted: 17 April 2018 at 1:55am

There will be a new forum dedicated to Sysinternals.
↧

Autoruns : Remove "File not Found"

April 17, 2018, 10:42 pm
$
0
0
Author: Aditza
Subject: Remove "File not Found"
Posted: 18 April 2018 at 5:42am

most of those "file not found" are actually present but loaded as part of the kernel, they are sub-systems loaded from a single monolithic file that provides multiple services needed by the kernel (i think it's win32k.sys if i remember correctly).


some non-windows related "file not found" entries are safe to disable if they have a path and can be identified as left-over from programs that used to be installed in \program files\

BUT, you should keep them if they DON'T have a path or they point to somewhere in the system area. If you don't know EXACTLY what the "missing" file is for then don't touch it.

If you disable some critical system-related "file not found" entries good luck trying to boot, you will probably need to re-install.
↧
↧

BgInfo : Not working for non-admin

April 18, 2018, 5:15 am
$
0
0
Author: cantoris
Subject: Not working for non-admin
Posted: 18 April 2018 at 12:15pm

On our Windows 10 (x64 Pro b1709) machines, BgInfo doesn't work for non-admin users.  We have it loading and being passed a BGI file via a command line from the Startup folder of the Start Menu.  This works fine on our Windows 7 kit.  On Windows 10, but only for non-admin, the wallpaper doesn't change.  There is no error message.
If you open the app as an affected non-admin user and load a BGI file, you can Preview the end result correctly but when you click Apply, nothing visibly happens.  It's set to appear on all monitors.
 
There are no Access Denied messages in ProcMon from BgInfo.
 
I've reproduced this in v4.24 and v4.25.  It also occurs on machines with no third-party antivirus installed.  It does it on various hardware and in a basic VM too.
 
Are others seeing this?
↧

BgInfo : Not working for non-admin

April 18, 2018, 7:13 am
$
0
0
Author: CRzz
Subject: Not working for non-admin
Posted: 18 April 2018 at 2:13pm

Perhaps the generated BMP or whatever BGinfo is generating is creating it somewhere where your users do not have proper access.
I have seen this on my domain computer when I use my "user" account.
Perhaps change the location where BGinfo is suppose to create the new picture...

Have you had any issues with tiled wallpapers?
Cause we use the same build of Win10 and noone seem to have been able to fix that.
According to many sites one should change the DPI settings but that does nothing and some of our users might want everything at a higher setting.
↧

BgInfo : Not working for non-admin

April 18, 2018, 8:21 am
$
0
0
Author: cantoris
Subject: Not working for non-admin
Posted: 18 April 2018 at 3:21pm

Thanks for the reply.
I've just been investigating and it creates the file in the user's temp folder - where they of course have write access.
***  For an affected user, the bitmap file DOES actually get created correctly in the right folder and it also gets set in  HKCU\Control Panel\Desktop\WallPaper, it just doesn't get physically applied as the wallpaper!  ***
 
I've reproduced this just now on a 32-bit clean install of 1709 too, as well as the 64-bit I was on before.
 
We've previously had issues with wallpapers becoming tiled in the presence of scaling settings over 125%, but that was fixed in recent BgInfo updates.
↧
Search

Miscellaneous Utilities : Sysmon - using condition "image" vs "is"

April 18, 2018, 9:18 am
$
0
0
Author: Nemo7891
Subject: Sysmon - using condition "image" vs "is"
Posted: 18 April 2018 at 4:18pm

Wondering if there is an explanation for this and if not, maybe it'll help someone down the line.

I was working on creating exclusions for Event ID 3 on a server that sent/received a ton of UDP traffic using java. It's part of an internally developed product and we have a way to simulate high load (more traffic). With an exclusion that looked like this:
<Image condition="is">C:\path\to\java.exe</Image>
even though the excluded events weren't being logged, sysmon was utilizing upwards of 30% CPU when the java app was under heavy load. I was ready to give up on it and turn off network connection monitoring when we changed the "is" to "image":
<Image condition="image">C:\path\to\java.exe</Image>
And suddenly under identical and even higher load, sysmon never went above 5%.

I suspect the reason it was so high initially was because while it knew not to log the event, it still had to analyze each event against a set of exclusions and somehow using "image" vs "is" is much more efficient, but would love an official explanation because I could not find anything documented.
↧
↧

Process Explorer : ** Process Explorer Bugs **

April 18, 2018, 10:21 am
$
0
0
Author: fuggetabouttiti
Subject: ** Process Explorer Bugs **
Posted: 18 April 2018 at 5:21pm

More crashes....

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: procexp64.exe
  Application Version: 16.21.0.0
  Application Timestamp: 59067242
  Fault Module Name: procexp64.exe
  Fault Module Version: 16.21.0.0
  Fault Module Timestamp: 59067242
  Exception Code: c0000005
  Exception Offset: 000000000004a8db
  OS Version: 6.1.7601.2.1.0.18.10
  Locale ID: 1033
  Additional Information 1: 5b3e
  Additional Information 2: 5b3e15254f511b52476d8cf1732ae53d
  Additional Information 3: 4d54
  Additional Information 4: 4d54a899cb35cb1ac80a5b9565ac6862

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

↧

Process Explorer : Reliable Process Explorer Crash

April 18, 2018, 10:25 am
$
0
0
Author: fuggetabouttiti
Subject: Reliable Process Explorer Crash
Posted: 18 April 2018 at 5:25pm

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: procexp64.exe
  Application Version: 16.21.0.0
  Application Timestamp: 59067242
  Fault Module Name: procexp64.exe
  Fault Module Version: 16.21.0.0
  Fault Module Timestamp: 59067242
  Exception Code: c0000005
  Exception Offset: 000000000004a8db
  OS Version: 6.1.7601.2.1.0.18.10
  Locale ID: 1033
  Additional Information 1: 5b3e
  Additional Information 2: 5b3e15254f511b52476d8cf1732ae53d
  Additional Information 3: 4d54
  Additional Information 4: 4d54a899cb35cb1ac80a5b9565ac6862

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Happens whenever I leave it running.



Edited by fuggetabouttiti - 11 seconds ago at 5:26pm
↧

Process Explorer : Reliable Process Explorer Crash

April 18, 2018, 10:36 am
$
0
0
Author: fuggetabouttiti
Subject: Reliable Process Explorer Crash
Posted: 18 April 2018 at 5:36pm

....and if I try to run as admin, I get an immediate crash...

Faulting application name: procexp64.exe, version: 16.21.0.0, time stamp: 0x59067242
Faulting module name: procexp64.exe, version: 16.21.0.0, time stamp: 0x59067242
Exception code: 0xc000041d
Fault offset: 0x000000000004a8db
Faulting process id: 0x402e8
Faulting application start time: 0x01d3d73afe2c0106
Faulting application path: C:\Automate\sysinternals\procexp64.exe
Faulting module path: C:\Automate\sysinternals\procexp64.exe
Report Id: eb3f795c-432e-11e8-a43b-000c29b468a7
↧

Process Explorer : Reliable Process Explorer Crash

April 18, 2018, 1:03 pm
$
0
0
Author: fuggetabouttiti
Subject: Reliable Process Explorer Crash
Posted: 18 April 2018 at 8:03pm

Procexp must have voodoo sixth sense and knows I'm posting about it, because not (after I deleted the sysinternal registry key), if refuses to laungh AT ALL, EVER.  ...and gives me this...

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: procexp64.exe
  Application Version: 16.21.0.0
  Application Timestamp: 59067242
  Fault Module Name: procexp64.exe
  Fault Module Version: 16.21.0.0
  Fault Module Timestamp: 59067242
  Exception Code: c0000005
  Exception Offset: 000000000004a8db
  OS Version: 6.1.7601.2.1.0.18.10
  Locale ID: 1033
  Additional Information 1: 1e1c
  Additional Information 2: 1e1c7e64d22edc8451514997a4bc8380
  Additional Information 3: aad6
  Additional Information 4: aad615b6feda48a4d71c3afa7c9cca18

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

...and then....

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: procexp64.exe
  Application Version: 16.21.0.0
  Application Timestamp: 59067242
  Fault Module Name: procexp64.exe
  Fault Module Version: 16.21.0.0
  Fault Module Timestamp: 59067242
  Exception Code: c000041d
  Exception Offset: 000000000004a8db
  OS Version: 6.1.7601.2.1.0.18.10
  Locale ID: 1033
  Additional Information 1: 417f
  Additional Information 2: 417f471e247acb64591815913201f6da
  Additional Information 3: 13c2
  Additional Information 4: 13c28fc9fb03467b2ba33d5316b2fcc2

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt


Same with both 32 and 64 bit versions.


Edited by fuggetabouttiti - 2 hours 31 minutes ago at 8:04pm
↧
↧

BgInfo : Not working for non-admin

April 19, 2018, 5:36 am
$
0
0
Author: CRzz
Subject: Not working for non-admin
Posted: 19 April 2018 at 12:36pm

Odd that the wallpaper doesnt apply for you... it does all the time when it runs on my computer.

I have been testing too but another approach, changing the TileWallpaper value in the registry 1 --> 0 after bginfo has done it's thing. 
But it seems like next time bginfo runs it uses the already generated background which will make a terrible result.

↧

BgInfo : Dual Monitor Background Problem

April 19, 2018, 6:26 am
$
0
0
Author: CRzz
Subject: Dual Monitor Background Problem
Posted: 19 April 2018 at 1:26pm

I can confirm that this issue is on the latest version...
I've written what I have done here:

It would be nice if this could be fixed....

I know alternative app(I use it on my own computers... it uses widgets instead of generating a new BG) that do the same thing but I'm not sure if it's allowed to suggest other apps.

↧
Search

BgInfo : Background keeps being set as "Tile"

April 19, 2018, 6:29 am
$
0
0
Author: CRzz
Subject: Background keeps being set as "Tile"
Posted: 19 April 2018 at 1:29pm

Tried it that but no greater success, sometimes it keept the setting but BGinfo seem to generate a new picture based on the previously generated picture.... 
↧

BgInfo : Background keeps being set as "Tile"

April 19, 2018, 6:31 am
$
0
0
Author: bpurchell
Subject: Background keeps being set as "Tile"
Posted: 19 April 2018 at 1:31pm

I wish they would fix this, it seems like a fundamental configuration. BGInfo works great for desktops, but when you have machines whose resolution dynamically changes it causes issues. We've been forced to use a tool called "Desktop Info", but it isn't supported anymore and I'd really like to move away from it.

Here's to hoping they fix BGInfo in future releases. Thanks for the feedback!
↧
↧

BgInfo : Background keeps being set as "Tile"

April 19, 2018, 6:40 am
$
0
0
Author: CRzz
Subject: Background keeps being set as "Tile"
Posted: 19 April 2018 at 1:40pm

Then I would suggest Rainmeter instead, much better cause it uses widget like Ms did in Vista.
No headaches there at all... have been using it for a while at home and like it alot since one can get more info.
Like CPU temp, ram load, IP (int and ext), network load... you name it... 
↧

BgInfo : Background keeps being set as "Tile"

April 20, 2018, 4:06 am
$
0
0
Author: CRzz
Subject: Background keeps being set as "Tile"
Posted: 20 April 2018 at 11:06am

I've found something interesting, not sure how to solve it but hey somthing....

HKEY_CURRENT_USER\Control Panel\Desktop
"Wallpaper"="PATH TO GENERATED BG"

HKEY_CURRENT_USER\Software\Winternals\BGInfo
"Wallpaper"="PATH TO UNMODIFIED PICTURE"

- I've seen that the path to the unmodified picture sometimes points the the same picture as the generated picture.

First I thought that the issue was the fitting settings but apparently it's not.
I hope this will help mr developer in some degree unless your already aware of this...
↧

BgInfo : Bug? Reuse of generated BG

April 20, 2018, 7:40 am
$
0
0
Author: CRzz
Subject: Bug? Reuse of generated BG
Posted: 20 April 2018 at 2:40pm

Hi,

There seem to be a bug, have verified it on the version we are running now v4.16 and the latest version 4.25.
The bug is that sometimes the Wallpaper value at HKEY_CURRENT_USER\Software\Winternals\BGInfo is set to the same value as in HKEY_CURRENT_USER\Control Panel\Desktop.
Which means BGinfo will recreate the new BG based appone the old generated picture.

First I thought this was a wallpaper fitting issue and was focusing on changing it to something else then tile.
Some of our users have dual monitors and most of the users have a laptop that is undocked all the time.
The screenresolution are changed often because of this.

HKEY_CURRENT_USER\Control Panel\Desktop
"Wallpaper"="PATH TO GENERATED BG"

HKEY_CURRENT_USER\Software\Winternals\BGInfo
"Wallpaper"="PATH TO UNMODIFIED PICTURE"
↧
Viewing all 10386 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>