Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Change Home Network Name


  • Please log in to reply
8 replies to this topic

#1 WacoJohn

WacoJohn

  • Members
  • 57 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Granbury, TX
  • Local time:11:32 AM

Posted 28 July 2018 - 09:04 AM

Make and model of computer      Dell Inspiron 3521 laptop w10-64

How the computer is connected (wireless or wired)       wired

Make and model of Router               Netgear XR500

Approximate Distance From the router the PC is if its a wireless connection            n/a

What type of internet you have (Dsl, Cable, T-1,etc..)          cable

 

 

On my home network, every device is connected to a network named LAKESIDE except one laptop.  It is connected to one named NETWORK.  I would like to change that so they are all connected to one named LAKESIDE.  I found a supposed way to do it using secpol, but it did not work.  Maybe I did not use secpol correctly.

 

Here is the trouble computer:

 

Attached File  dell.PNG   12.33KB   0 downloads

 

Here is a good one:

 

Attached File  acer.PNG   18.01KB   0 downloads

 

Notice the names NETWORK and LAKESIDE.

 

Any help is appreciated in advance.

 

 

MiniToolBox by Farbar  Version: 17-06-2016

Ran by owner (administrator) on 28-07-2018 at 06:35:19
Running from "C:\Users\owner\Desktop"
Microsoft Windows 10 Home  (X64)
Model: Inspiron 3521 Manufacturer: Dell Inc.
Boot Mode: Normal
***************************************************************************
 
========================= Flush DNS: ===================================
 
Windows IP Configuration
 
Successfully flushed the DNS Resolver Cache.
 
========================= IE Proxy Settings: ============================== 
 
Proxy is not enabled.
No Proxy Server is set.
 
"Reset IE Proxy Settings": IE Proxy Settings were reset.
========================= Hosts content: =================================
========================= IP Configuration: ================================
 
Realtek PCIe FE Family Controller = Ethernet (Connected)
Dell Wireless 1704 802.11b/g/n (2.4GHz) = Wi-Fi (Media disconnected)
Bluetooth Device (Personal Area Network) = Bluetooth Network Connection (Media disconnected)
 
 
# ----------------------------------
# IPv4 Configuration
# ----------------------------------
pushd interface ipv4
 
reset
set global defaultcurhoplimit=64
set interface interface="Ethernet (Kernel Debugger)" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Ethernet" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Wi-Fi" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Local Area Connection* 2" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Bluetooth Network Connection" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
set interface interface="Local Area Connection* 1" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabled
 
 
popd
# End of IPv4 configuration
 
 
 
Windows IP Configuration
 
   Host Name . . . . . . . . . . . . : Dell-64
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
 
Wireless LAN adapter Wi-Fi:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Dell Wireless 1704 802.11b/g/n (2.4GHz)
   Physical Address. . . . . . . . . : F8-2F-A8-D9-C9-91
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Wireless LAN adapter Local Area Connection* 2:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
   Physical Address. . . . . . . . . : FA-2F-A8-D9-C9-91
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Wireless LAN adapter Local Area Connection* 1:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
   Physical Address. . . . . . . . . : FA-2F-A8-D9-C1-91
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
 
Ethernet adapter Ethernet:
 
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physical Address. . . . . . . . . : EC-F4-BB-0D-83-DB
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::1c03:124c:79ec:49bd%19(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.1.9(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, July 28, 2018 6:26:27 AM
   Lease Expires . . . . . . . . . . : Sunday, July 29, 2018 6:26:26 AM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 132969659
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-E9-2E-D7-EC-F4-BB-0D-83-DB
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
 
Ethernet adapter Bluetooth Network Connection:
 
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
   Physical Address. . . . . . . . . : F8-2F-A8-D9-C9-92
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Server:  UnKnown
Address:  192.168.1.1
 
Name:    google.com
Addresses:  2607:f8b0:4009:80e::200e
  172.217.5.14
 
 
Pinging google.com [172.217.8.206] with 32 bytes of data:
Reply from 172.217.8.206: bytes=32 time=42ms TTL=51
Reply from 172.217.8.206: bytes=32 time=46ms TTL=51
 
Ping statistics for 172.217.8.206:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 42ms, Maximum = 46ms, Average = 44ms
Server:  UnKnown
Address:  192.168.1.1
 
Name:    yahoo.com
Addresses:  2001:4998:44:41d::3
  2001:4998:58:1836::11
  2001:4998:c:1023::5
  2001:4998:c:1023::4
  2001:4998:58:1836::10
  2001:4998:44:41d::4
  98.138.219.231
  98.137.246.7
  72.30.35.9
  98.137.246.8
  98.138.219.232
  72.30.35.10
 
 
Pinging yahoo.com [72.30.35.10] with 32 bytes of data:
Reply from 72.30.35.10: bytes=32 time=60ms TTL=50
Reply from 72.30.35.10: bytes=32 time=59ms TTL=50
 
Ping statistics for 72.30.35.10:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 60ms, Average = 59ms
 
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
 
Ping statistics for 127.0.0.1:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
===========================================================================
Interface List
 11...f8 2f a8 d9 c9 91 ......Dell Wireless 1704 802.11b/g/n (2.4GHz)
 18...fa 2f a8 d9 c9 91 ......Microsoft Wi-Fi Direct Virtual Adapter
  3...fa 2f a8 d9 c1 91 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 19...ec f4 bb 0d 83 db ......Realtek PCIe FE Family Controller
 12...f8 2f a8 d9 c9 92 ......Bluetooth Device (Personal Area Network)
  1...........................Software Loopback Interface 1
===========================================================================
 
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1      192.168.1.9     35
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      192.168.1.0    255.255.255.0         On-link       192.168.1.9    291
      192.168.1.9  255.255.255.255         On-link       192.168.1.9    291
    192.168.1.255  255.255.255.255         On-link       192.168.1.9    291
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
        224.0.0.0        240.0.0.0         On-link       192.168.1.9    291
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link       192.168.1.9    291
===========================================================================
Persistent Routes:
  None
 
IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    331 ::1/128                  On-link
 19    291 fe80::/64                On-link
 19    291 fe80::1c03:124c:79ec:49bd/128
                                    On-link
  1    331 ff00::/8                 On-link
 19    291 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
========================= Winsock entries =====================================
 
Catalog5 01 C:\WINDOWS\SysWOW64\napinsp.dll [54784] (Microsoft Corporation)
Catalog5 02 C:\WINDOWS\SysWOW64\pnrpnsp.dll [70656] (Microsoft Corporation)
Catalog5 03 C:\WINDOWS\SysWOW64\pnrpnsp.dll [70656] (Microsoft Corporation)
Catalog5 04 C:\WINDOWS\SysWOW64\NLAapi.dll [64000] (Microsoft Corporation)
Catalog5 05 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog5 06 C:\WINDOWS\SysWOW64\winrnr.dll [24064] (Microsoft Corporation)
Catalog5 07 C:\WINDOWS\SysWOW64\wshbth.dll [51712] (Microsoft Corporation)
Catalog9 01 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 02 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 03 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 04 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 05 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 06 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 07 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 08 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 09 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 10 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 11 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 12 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 13 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
Catalog9 14 C:\WINDOWS\SysWOW64\mswsock.dll [341920] (Microsoft Corporation)
x64-Catalog5 01 C:\Windows\System32\napinsp.dll [67072] (Microsoft Corporation)
x64-Catalog5 02 C:\Windows\System32\pnrpnsp.dll [84992] (Microsoft Corporation)
x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [84992] (Microsoft Corporation)
x64-Catalog5 04 C:\Windows\System32\NLAapi.dll [80896] (Microsoft Corporation)
x64-Catalog5 05 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog5 06 C:\Windows\System32\winrnr.dll [31232] (Microsoft Corporation)
x64-Catalog5 07 C:\Windows\System32\wshbth.dll [63488] (Microsoft Corporation)
x64-Catalog9 01 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 02 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 03 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 04 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 05 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 06 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 07 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 08 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 09 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 10 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 11 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 12 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 13 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
x64-Catalog9 14 C:\Windows\System32\mswsock.dll [401968] (Microsoft Corporation)
 
========================= Event log errors: ===============================
 
Application errors:
==================
Error: (07/26/2018 12:38:30 PM) (Source: Microsoft-Windows-RestartManager) (User: DELL-64)
Description: Application or service 'Dell Client Management Service' could not be restarted.
 
Error: (07/26/2018 12:11:27 PM) (Source: MsiInstaller) (User: DELL-64)
Description: Product: Dell SupportAssist -- Installer User Interface mode not supported.
 
Error: (07/26/2018 12:11:16 PM) (Source: MsiInstaller) (User: DELL-64)
Description: Product: Dell SupportAssist -- Installer User Interface mode not supported.
 
Error: (07/26/2018 07:22:13 AM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW.  hr = 0x8007001f, A device attached to the system is not functioning.
.
 
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet
 
Error: (07/26/2018 06:19:57 AM) (Source: Application Error) (User: )
Description: Faulting application name: syntpenh.exe, version: 19.2.17.64, time stamp: 0x5a35d26a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002c89ca0
Faulting process id: 0xec
Faulting application start time: 0xsyntpenh.exe0
Faulting application path: syntpenh.exe1
Faulting module path: syntpenh.exe2
Report Id: syntpenh.exe3
Faulting package full name: syntpenh.exe4
Faulting package-relative application ID: syntpenh.exe5
 
Error: (07/25/2018 07:58:27 PM) (Source: SyncUpdater) (User: )
Description: Failed to stop service. System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort()
   at SyncUpdaterService.SyncUpdaterLogic.stopMailslotWatcherThread()
   at SyncUpdaterService.SyncUpdater.OnStop()
   at System.ServiceProcess.ServiceBase.DeferredStop()
 
Error: (07/25/2018 07:55:50 PM) (Source: VSS) (User: )
Description: Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW.  hr = 0x80070006, The handle is invalid.
.
 
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet
 
Error: (07/25/2018 05:25:39 PM) (Source: MSDTC Client 2) (User: )
Description: 0x8007085A
 
Error: (07/25/2018 05:22:48 PM) (Source: MSDTC Client 2) (User: )
Description: 0x8007085A
 
Error: (07/25/2018 05:22:48 PM) (Source: MSDTC 2) (User: )
Description: 0x8007085A
 
 
System errors:
=============
Error: (07/28/2018 06:31:47 AM) (Source: DCOM) (User: DELL-64)
Description: application-specificLocalActivation{D63B10C5-BB46-4990-A94F-E40B9D520160}{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}DELL-64ownerS-1-5-21-216590880-3608650652-1323539550-1001LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/28/2018 06:28:22 AM) (Source: DCOM) (User: NT AUTHORITY)
Description: application-specificLocalLaunchWindows.SecurityCenter.WscBrokerManagerUnavailableNT AUTHORITYSYSTEMS-1-5-18LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/28/2018 06:27:04 AM) (Source: DCOM) (User: NT AUTHORITY)
Description: application-specificLocalActivation{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}NT AUTHORITYLOCAL SERVICES-1-5-19LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/28/2018 06:27:04 AM) (Source: DCOM) (User: NT AUTHORITY)
Description: application-specificLocalActivation{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}NT AUTHORITYLOCAL SERVICES-1-5-19LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/28/2018 06:27:03 AM) (Source: DCOM) (User: NT AUTHORITY)
Description: application-specificLocalActivation{D63B10C5-BB46-4990-A94F-E40B9D520160}{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}NT AUTHORITYLOCAL SERVICES-1-5-19LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/28/2018 06:26:28 AM) (Source: Service Control Manager) (User: )
Description: The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: 
%%1058 = The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
 
 
Error: (07/28/2018 03:22:40 AM) (Source: DCOM) (User: NT AUTHORITY)
Description: application-specificLocalActivation{D63B10C5-BB46-4990-A94F-E40B9D520160}{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}NT AUTHORITYLOCAL SERVICES-1-5-19LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/27/2018 06:23:32 PM) (Source: DCOM) (User: DELL-64)
Description: application-specificLocalActivation{D63B10C5-BB46-4990-A94F-E40B9D520160}{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}DELL-64ownerS-1-5-21-216590880-3608650652-1323539550-1001LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/27/2018 05:41:28 PM) (Source: DCOM) (User: DELL-64)
Description: application-specificLocalActivation{D63B10C5-BB46-4990-A94F-E40B9D520160}{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}DELL-64ownerS-1-5-21-216590880-3608650652-1323539550-1001LocalHost (Using LRPC)UnavailableUnavailable
 
Error: (07/27/2018 05:28:32 PM) (Source: DCOM) (User: NT AUTHORITY)
Description: application-specificLocalLaunchWindows.SecurityCenter.WscDataProtectionUnavailableNT AUTHORITYSYSTEMS-1-5-18LocalHost (Using LRPC)UnavailableUnavailable
 
 
Microsoft Office Sessions:
=========================
Error: (07/26/2018 12:38:30 PM) (Source: Microsoft-Windows-RestartManager)(User: DELL-64)
Description: 0ServiceShell.exeDell Client Management Service03026217871800
 
Error: (07/26/2018 12:11:27 PM) (Source: MsiInstaller)(User: DELL-64)
Description: Product: Dell SupportAssist -- Installer User Interface mode not supported.(NULL)(NULL)(NULL)(NULL)(NULL)
 
Error: (07/26/2018 12:11:16 PM) (Source: MsiInstaller)(User: DELL-64)
Description: Product: Dell SupportAssist -- Installer User Interface mode not supported.(NULL)(NULL)(NULL)(NULL)(NULL)
 
Error: (07/26/2018 07:22:13 AM) (Source: VSS)(User: )
Description: QueryFullProcessImageNameW0x8007001f, A device attached to the system is not functioning.
 
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet
 
Error: (07/26/2018 06:19:57 AM) (Source: Application Error)(User: )
Description: syntpenh.exe19.2.17.645a35d26aunknown0.0.0.000000000c00000050000000002c89ca0ec01d424e3582a12f6C:\program files\synaptics\syntp\syntpenh.exeunknown548b8236-8749-474f-bbda-f298f6ebac8f
 
Error: (07/25/2018 07:58:27 PM) (Source: SyncUpdater)(User: )
Description: Failed to stop service. System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort()
   at SyncUpdaterService.SyncUpdaterLogic.stopMailslotWatcherThread()
   at SyncUpdaterService.SyncUpdater.OnStop()
   at System.ServiceProcess.ServiceBase.DeferredStop()
 
Error: (07/25/2018 07:55:50 PM) (Source: VSS)(User: )
Description: QueryFullProcessImageNameW0x80070006, The handle is invalid.
 
 
Operation:
   Executing Asynchronous Operation
 
Context:
   Current State: DoSnapshotSet
 
Error: (07/25/2018 05:25:39 PM) (Source: MSDTC Client 2)(User: )
Description: 0x8007085A
 
Error: (07/25/2018 05:22:48 PM) (Source: MSDTC Client 2)(User: )
Description: 0x8007085A
 
Error: (07/25/2018 05:22:48 PM) (Source: MSDTC 2)(User: )
Description: 0x8007085A
 
 
CodeIntegrity Errors:
===================================
  Date: 2018-07-26 06:55:16.797
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:55:16.302
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:55:00.693
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:54:51.899
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:54:51.384
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:54:42.268
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:54:40.526
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-26 06:54:40.525
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-25 17:38:03.186
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
  Date: 2018-07-25 17:38:02.671
  Description: Code Integrity determined that a process (\Device\HarddiskVolume3\Windows\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\MicrosoftEdgeCP.exe) attempted to load \Device\HarddiskVolume3\Program Files\Malwarebytes\Anti-Malware\mbae64.dll that did not meet the Store signing level requirements.
 
 
=========================== Installed Programs ============================
 
7-Zip 18.05 (x64) (HKLM\...\7-Zip) (Version: 18.05 - Igor Pavlov)
8GadgetPack (HKLM-x32\...\{36E60904-D465-40F7-82A7-A9C7A84C29B7}) (Version: 24.0.0 - 8GadgetPack.net)
Adobe Flash Player 30 PPAPI (HKLM-x32\...\Adobe Flash Player PPAPI) (Version: 30.0.0.134 - Adobe Systems Incorporated)
Advanced SystemCare 11 (HKLM-x32\...\Advanced SystemCare_is1) (Version: 11.4.0 - IObit)
Backup and Sync from Google (HKLM\...\{AEFBDB5B-899F-4AE6-B789-BA56A652A476}) (Version: 3.42.9858.3671 - Google, Inc.)
BleachBit (HKLM-x32\...\BleachBit) (Version: 2.0 - BleachBit)
Box Sync (HKLM\...\{BFA57077-F78C-4B92-815E-7BCDA6B9686E}) (Version: 4.0.7911.0 - Box, Inc.)
Box Sync (HKLM-x32\...\{f4c1fa3e-f9c6-413c-8663-31feeb45811f}) (Version: 4.0.7900.0 - Box Inc.) Hidden
Brother MFL-Pro Suite MFC-7440N (HKLM-x32\...\{46E1B1F2-A279-4356-9B17-029F9CC72EAE}) (Version: 2.0.0.0 - Brother Industries, Ltd.)
CCleaner (HKLM\...\CCleaner) (Version: 5.45 - Piriform)
Dell SupportAssist (HKLM\...\{4CB4741A-20C1-454E-8276-993D06A76D67}) (Version: 2.2.3.2 - Dell Inc.)
Dell Touchpad (HKLM\...\SynTPDeinstKey) (Version: 19.2.17.64 - Synaptics Incorporated)
Dell Update (HKLM-x32\...\{5EBBC1DA-975F-44A0-B438-F325BCD45577}) (Version: 3.0.0 - Dell Inc.)
Dropbox (HKLM-x32\...\Dropbox) (Version: 53.4.67 - Dropbox, Inc.)
Dropbox Update Helper (HKLM-x32\...\{099218A5-A723-43DC-8DB5-6173656A1E94}) (Version: 1.3.75.1 - Dropbox, Inc.) Hidden
Duplicate Cleaner Pro 4.1.0 (HKLM-x32\...\Duplicate Cleaner Pro) (Version: 4.1.0 - DigitalVolcano Software Ltd)
EaseUS Todo Backup Home 11.0 (HKLM-x32\...\EaseUS Todo Backup_is1) (Version: 11.0 - CHENGDU YIWO Tech Development Co., Ltd)
Evernote v. 6.13.14 (HKLM-x32\...\{D16B1D50-7D70-11E8-81F3-005056951CAD}) (Version: 6.13.14.7474 - Evernote Corp.)
Foxit Reader (HKLM-x32\...\Foxit Reader_is1) (Version: 9.2.0.9297 - Foxit Software Inc.)
Glary Utilities 5.102 (HKLM-x32\...\Glary Utilities 5) (Version: 5.102.0.124 - Glarysoft Ltd)
GoodSync (HKLM\...\{B26B00DA-2E5D-4CF2-83C5-911198C0F009}) (Version: 10.9.2.2 - Siber Systems)
Google Update Helper (HKLM-x32\...\{60EC980A-BDA2-4CB6-A427-B07A5498B4CA}) (Version: 1.3.33.17 - Google Inc.) Hidden
IObit Uninstaller (HKLM-x32\...\IObitUninstall) (Version: 7.5.0.7 - IObit)
Java 8 Update 181 (HKLM-x32\...\{26A24AE4-039D-4CA4-87B4-2F32180181F0}) (Version: 8.0.1810.13 - Oracle Corporation)
LastPass (uninstall only) (HKLM-x32\...\LastPass) (Version:  - LastPass)
LastPass for Applications (HKLM-x32\...\LastApp) (Version:  - LastPass)
Malwarebytes version 3.5.1.2522 (HKLM\...\{35065F43-4BB2-439A-BFF7-0F1014F2E0CD}_is1) (Version: 3.5.1.2522 - Malwarebytes)
Microsoft OneDrive (HKCU\...\OneDriveSetup.exe) (Version: 18.111.0603.0006 - Microsoft Corporation)
PatchCleaner (HKLM-x32\...\{727DA176-50BB-452C-8DB5-96EE0A573ED4}) (Version: 1.4.20 - HomeDev)
PNotes.NET 3.7.0.4 (HKLM-x32\...\{02384F4C-1820-49E9-9D03-81F27EEE1224}_is1) (Version: 3.7.0.4 - Andrey Gruber)
Realtek High Definition Audio Driver (HKLM-x32\...\{F132AF7F-7BCA-4EDE-8A7C-958108FE7DBC}) (Version: 6.0.1.8186 - Realtek Semiconductor Corp.)
Revo Uninstaller 2.0.5 (HKLM\...\{A28DBDA2-3CC7-4ADC-8BFE-66D7743C6C97}_is1) (Version: 2.0.5 - VS Revo Group, Ltd.)
Send To Toys v2.71 (HKLM\...\Send To Toys_is1) (Version:  - Gabriele Ponti)
SES Driver (HKLM\...\{D8CC254C-C671-4664-9A38-FA368D1E2C97}) (Version: 1.0.0 - Western Digital)
Smart Defrag 6 (HKLM-x32\...\Smart Defrag_is1) (Version: 6.0 - IObit)
SmartByte Drivers and Services (HKLM\...\{EC62F71A-6CFA-4918-9EBC-99BFF86DB3C9}) (Version: 1.2.600 - Rivet Networks)
SMPlayer 18.6.0 (x64) (HKLM\...\SMPlayer) (Version: 18.6.0 - Ricardo Villalba)
SRWare Iron (64-Bit) version 67.0.3500.0 (HKLM\...\{BA85A29D-B48E-4826-BAEE-817024E52E29}_is1) (Version: 67.0.3500.0 - SRWare)
Super Finder XT  2.6.3.2 (HKLM-x32\...\Super Finder XT Supporters Edition_is1) (Version:  - FSL - FreeSoftLand)
TeamViewer 13 (HKLM-x32\...\TeamViewer) (Version: 13.2.5287 - TeamViewer)
Update for Windows 10 for x64-based Systems (KB4023057) (HKLM\...\{5009B7EE-8A15-4A23-B404-15E31D02DA67}) (Version: 2.43.0.0 - Microsoft Corporation)
Windows Driver Package - Western Digital Technologies (WDC_SAM) WDC_SAM  (01/19/2011 1.0.0009.0) (HKLM\...\4CA7CFBB29889F25ACB3DF6E3A42BAE29EB43B20) (Version: 01/19/2011 1.0.0009.0 - Western Digital Technologies)
Windows Setup Remediations (x64) (KB4023057) (HKLM\...\{5534e02f-0f5d-40dd-ba92-bea38d22384d}.sdb) (Version:  - )
 
========================= Devices: ================================
 
 
========================= Memory info: ===================================
 
Percentage of memory in use: 50%
Total physical RAM: 8073.27 MB
Available physical RAM: 4024.52 MB
Total Virtual: 9993.27 MB
Available Virtual: 5014.97 MB
 
========================= Partitions: =====================================
 
1 Drive c: (Windows) (Fixed) (Total:464.8 GB) (Free:425.96 GB) NTFS
2 Drive d: (250GB) (Fixed) (Total:232.89 GB) (Free:210.03 GB) NTFS
4 Drive f: (DellDriveF) (Fixed) (Total:2794.49 GB) (Free:2686.97 GB) NTFS
5 Drive g: (TOSHIBA EXT) (Fixed) (Total:465.76 GB) (Free:435.57 GB) NTFS
 
========================= Users: ========================================
 
User accounts for \\DELL-64
 
Administrator            DefaultAccount           Guest                    
owner                    WDAGUtilityAccount       
 
========================= Minidump Files ==================================
 
No minidump file found
 
========================= Restore Points ==================================
 
26-07-2018 07:39:46 Windows Update
26-07-2018 14:07:12 Windows Modules Installer
26-07-2018 14:07:53 Windows Modules Installer
26-07-2018 14:08:33 Windows Modules Installer
26-07-2018 14:09:01 Windows Modules Installer
26-07-2018 14:32:23 Installed PatchCleaner
26-07-2018 18:57:58 Installed Dell SupportAssist.
26-07-2018 19:27:26 Installed Dell Update.
 
**** End of log ****
 

 



BC AdBot (Login to Remove)

 


#2 britechguy

britechguy

    Been there, done that, got the T-shirt


  • Moderator
  • 9,019 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Staunton, VA
  • Local time:12:32 PM

Posted 28 July 2018 - 09:22 AM

And I'll bet that every device other than the one you're talking about is connected via WiFi.

 

WiFi networks are assigned network names (SSIDs) while wired networks are not since they are direct connect.  You don't have multiple potential wired networks "over the air" to choose from, you choose one by plugging in to its wiring.

 

I have never seen a wired connection called anything but "Network" and if the machine connected by wire is connected to the same router (and you haven't created a subnet arrangement) all of the machines are on the same network already.  The ones connected via WiFi use SSID Lakeside to connect to it while any connected by wire are simply connected to Network.

 

Try turning off WiFi and plugging in one of your other devices by wire and you'll see that it's connected to "Network" too.

 

If, however, you absolutely must make this change, it's going to require a registry tweak or use local security policy.  See:

 

https://www.tenforums.com/tutorials/28375-change-network-profile-name-windows-10-a.html

 

https://winaero.com/blog/how-to-rename-network-profile-in-windows-10/

 

 

P.S.:  In the future, please do not use MiniToolBox nor post logs from same unless requested to do so by a member of staff.  


Edited by britechguy, 28 July 2018 - 09:24 AM.
Added P.S.

Brian  AKA  Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134 

     . . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it.  The willing suspension of disbelief has its limits, or should.

    ~ Ruth Marcus,  November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story


 

 

 

              

 


#3 mikey11

mikey11

  • Members
  • 1,509 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Psychiatric Ward @ Beelitz-Heilstatten Hospital, Beelitz, Germany
  • Local time:06:32 PM

Posted 28 July 2018 - 10:12 AM

 

 

 

On my home network, every device is connected to a network named LAKESIDE except one laptop.  It is connected to one named NETWORK

 

 

 

that is normal for a wired connection



#4 WacoJohn

WacoJohn
  • Topic Starter

  • Members
  • 57 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Granbury, TX
  • Local time:11:32 AM

Posted 28 July 2018 - 10:18 AM

Hmmm.  Well, there are 4 computers wired.  1 computer WiFi.  Then several other devices (Alexa, TV sound bar, Tivo) connected WiFi. 

 

Everything, as much as I can tell are connected to LAKESIDE except the computer in question which is connected to "NETWORK" and is wired. 

 

Sorry about the Minibox post.  I thought I read a sticky to always include it.  I apologize.

 

As for the links you provided ... I will wait until we get some of the confusion cleared up if you don't mind.

 

I don't know if it has to do with this NAME issue, but I am having some really goofy behaviors as to these computers being effectively accessing each other.  File and printer sharing is on ... I have checked that many times ... but I am unable for all devices to connect to each other the same way, machine to machine.  That is what lead me to discover the naming difference.

 

Edit:

 

Mikey,

 

 

​​that is normal for a wired connection

​


I am getting different name on one wired computer than I get on other wired computers.

Edited by WacoJohn, 28 July 2018 - 10:25 AM.


#5 mikey11

mikey11

  • Members
  • 1,509 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Psychiatric Ward @ Beelitz-Heilstatten Hospital, Beelitz, Germany
  • Local time:06:32 PM

Posted 28 July 2018 - 10:23 AM

Hmmm.  Well, there are 4 computers wired.

 

check all 4 wired computers.....they should all be connected to "network"


Edited by mikey11, 28 July 2018 - 10:23 AM.


#6 WacoJohn

WacoJohn
  • Topic Starter

  • Members
  • 57 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Granbury, TX
  • Local time:11:32 AM

Posted 28 July 2018 - 10:26 AM

3 are LAKESIDE and one is NETWORK.



#7 britechguy

britechguy

    Been there, done that, got the T-shirt


  • Moderator
  • 9,019 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Staunton, VA
  • Local time:12:32 PM

Posted 28 July 2018 - 10:31 AM

Then I'll be willing to bet that the computers that you think have a wired connection (and actually are plugged in) are using WiFi instead.

 

As has been pointed out, the default behavior under Windows is that wired connections get called "Network."  SSIDs are not used, and "Lakeside" appears to be an SSID.

 

You need to make sure that your connection is what you think it is and intentionally disable any internal wireless cards on the devices connected by wire (or else make sure that the WiFi network "Lakeside" has been intentionally forgotten for the WiFi adapters on those devices).


Brian  AKA  Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134 

     . . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it.  The willing suspension of disbelief has its limits, or should.

    ~ Ruth Marcus,  November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story


 

 

 

              

 


#8 WacoJohn

WacoJohn
  • Topic Starter

  • Members
  • 57 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Granbury, TX
  • Local time:11:32 AM

Posted 28 July 2018 - 10:49 AM

I totally believe all of you.  You are experts, and I am far from it.  Here is ONE of the wired computers connected to LAKESIDE:

 

Attached File  LAKESIDE.PNG   19.35KB   0 downloads

 

Attached File  lakeside2.PNG   21.75KB   0 downloads

 

and, in fact, its HARDWARE switch for WiFi is off.

 

I am not arguing.  I am beginning to think I have a somewhat exotic problem.  Thanks again for the help.



#9 britechguy

britechguy

    Been there, done that, got the T-shirt


  • Moderator
  • 9,019 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Staunton, VA
  • Local time:12:32 PM

Posted 28 July 2018 - 12:03 PM

Who configured all this to start with?   The only way I know of to have the situation you gave the screen shots for is if someone did go through the process of doing one of the tweaks I gave links to earlier to rename the network, otherwise a wired network should be named "Network" under Windows.

 

In any case, circling all the way back to the beginning, why does this matter?   In actuality, regardless of what the network name is shown as, if all of these devices are using one access point, whether by wire or wireless, and no one has set up subnets (which is unlikely) they are all connected to the same LAN regardless of what name is showing.  All should be visible to each other if sharing options are configured such that they are, and if you have a "mixed Windows environment" (some Win7 and some Win10, say) how one configures things differs somewhat as security became tighter on Windows 10 than it had been in earlier versions of Windows.  If you look at the router's network map page you should see each and every device in the devices list, most likely with either 192.168.1.X addresses or 10.0.0.X addresses (the former is very common for a great many routers that are not cable-based while the latter is big on the Arris and similar lines of cable modem-routers).

 

I guess I'm asking whether it's the network name that's critical or the ability to network the computers as you'd like them critical.  If it's the latter, that's where I'd put my energy.


Edited by britechguy, 28 July 2018 - 12:05 PM.

Brian  AKA  Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1803, Build 17134 

     . . . the presumption of innocence, while essential in the legal realm, does not mean the elimination of common sense outside it.  The willing suspension of disbelief has its limits, or should.

    ~ Ruth Marcus,  November 10, 2017, in Washington Post article, Bannon is right: It’s no coincidence The Post broke the Moore story


 

 

 

              

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users