Unknown MAC / IP addresses and device
I've got an unconfirmed device listed in my network monitoring app. It has MAC and IP addresses that I can't identify, so I can't determine who owns this device. So, I don't know if it's one of my devices or someone has wormed their way into my Wi-Fi. It's online occasionally. Is there any way to determine what this actual device is? The MAC address is 22:8D:4F:AF:2B:38. The network monitoring app says it's a mobile, the vendor is android-dhcp-10, the brand is Google and its model / version is Android 10. It also says that the DHCP params (whatever they are??) are 1, 3, 6, 15, 26, 28, 51, 58, 59, 43. On the network monitoring app devices summary page the model and name fields are empty. Any help would be appreciated. Thank you.
Windows 11 25H2 "Point in time restore" seems to reset System Protection to 2%
TL;DR: On Windows 11 25H2, the new "Point in time restore" feature (Settings > System > Recovery) shares a single VSS shadow-storage allocation with classic System Restore. It periodically re-applies its own default of ~2% of the volume, which overrides the System Protection "Max Usage" I set and purges existing restore points - and it does this even when the feature is turned off. I'd like to confirm whether others see this and whether it is by design. Environment Windows 11 Pro, 25H2 (build 26200.8875) Single internal SSD, C: ~488 GB, NTFS "Point in time restore" was enabled by a recent update without my action; I had since turned it off. Symptom I set System Protection (System Protection > Configure > "Max Usage") for C: to 6%. Within a day or two it silently reverts to exactly 2% of the volume (9.76 GB on my 488 GB drive). When it drops, VSS deletes older restore points to fit the smaller cap - visible in Event Viewer, System log, source volsnap, Event ID 33 ("The oldest shadow copy of volume C: was deleted to keep disk space usage ... below the user defined limit"). So I lose restore history I was relying on. It resets to exactly 2% every time - a computed default, not a random value. What I found: the two features share ONE allocation (reproducible) There is a single VSS shadow-copy storage association for C: with one Maximum. Classic System Restore and "Point in time restore" are two front-ends to that same number: Elevated prompt: vssadmin list shadowstorage - note "Maximum Shadow Copy Storage space" for C:. Settings > System > Recovery > Point in time restore - set its size (I used 15 GB). Re-run vssadmin list shadowstorage - the Maximum is now 15 GB, and the classic System Protection "Max Usage" now also shows 15 GB. So setting Point-in-time's allocation writes the same maximum System Restore uses. The reset to 2% is therefore Point-in-time re-applying its own default to that shared allocation - which is why my System Protection setting keeps getting overridden and restore points get purged. Two details that stand out It resets even with the feature OFF. Point-in-time had been disabled for about two weeks (its stored allocation left at the 2% default) and the reset still happened. So a background component re-applies the 2% regardless of the on/off toggle. The coupling is one-way. Setting the value via Point-in-time updates both; setting it via classic System Protection updates the live maximum but does not update Point-in-time's stored value. Point-in-time keeps its own independent allocation, and that stored value is what gets re-applied. What it is NOT Not a Windows Update / servicing event - no quality or feature update installed on the days it reset (only Microsoft Defender definition updates, which do not touch System Protection). No reboot, crash, or third-party backup software involved. Mechanism, as I understand it "Point in time restore" appears to be a whole-volume revert - it reboots into WinRE (the Recovery partition) and rolls the entire C: volume back to a snapshot - whereas classic System Restore is a selective restore of the registry and system files that runs from the live OS. Both use the same VSS shadow copies of C:, which is why they share one storage allocation. (I am confident about the shared-allocation and reset behaviour, which is reproducible above; the internal revert mechanism is my inference.) Questions Is Point-in-time overriding the user's System Protection allocation, and purging restore points to fit, by design? How can the System Protection "Max Usage" be made to persist - i.e. stop Point-in-time re-applying its 2% default? Can Point-in-time's allocation be raised, or its re-assertion disabled, without disabling classic System Restore? Is there a supported registry or policy setting for this? I could find no honored DiskPercent / percentage value on 25H2. If you want to check your own machine Run vssadmin list shadowstorage (elevated) before and after setting Point-in-time's size, and watch whether your System Protection "Max Usage" holds over a few days or reverts to ~2%. I'd appreciate confirmation - or contradiction - as I'm trying to establish whether this is universal 25H2 behaviour or specific to my setup. Thanks!
